microsoft / microsoft/Analysis-Services
403 Forbidden Error When Calling New-FabricWorkspace in PowerShell – Was Working Earlier
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 732
- Forks
- 433
- PR merge metrics
- No merged PRs in 30d
Description
Hi Team,
I'm encountering an issue while trying to call the Fabric REST API to create/get a workspace ID using PowerShell. The script was working fine until 19-May-2025, but it started failing from 20-May-2025 with the following error:
powershell
Import-Module ".\modules\FabricPS-PBIP" -Force
$workspaceId = New-FabricWorkspace -name $workspaceName -skipErrorIfExists
The second line throws below exception:
Exception: Response status code does not indicate success: 403 (Forbidden).; API error code: 'FeatureNotAvailable'
I have an App Registration created in Azure and am using that spn for authentication.
No changes were made to the script or permissions from my side around the time the issue started.
Could someone please help me understand why this error is occurring now? Was there any recent change in Fabric API availability, permissions, or licensing that could cause this?
Thanks in advance!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the New-FabricWorkspace call in the FabricPS-PBIP module and reproduce the 403 response using the shown script. Check the Fabric REST API's current availability, service-principal permissions, and licensing requirements for the FeatureNotAvailable error. Done means identifying the relevant external requirement or confirming a repository-side fix is needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, powershell
- Domain
- api, authentication, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100