Invoke-PowerBIRestMethod Invalid URL

[azocc]

So I'm a Tennent admin and I am an admin in 3 workspaces (premium capacity) that are part of a deployment pipeline, but I can not see the pipeline.  The admin who created has left the company.  I did find this API REST approach, but when I run it high side...

Invoke-PowerBIRestMethod -url "https://app.high.powerbigov.us/v1.0/myorg/admin/pipelines?$expand=stages&$top=100" -Method GET

I get a returned error:

Power BI

We couldn't find the page you were looking for.
TECHNICAL DETAILS
An unknown error occurred. If you continue to see this error, please provide the following informat ion when requesting support.
Date and Time: 2026-03-26 18:50:53Z
Activity Id: 7c8a472a-b725-4ce5-9d93-c96f3e23420a
Go back home

Is it possible to run Invoke-PowerBIRestMethod on highgov?

Any other way to get access to a pipeline?

Some additional info:  I do use powershell for cmdlets and can connect and execute.  it's just the Rest calls that error.

[azocc]

The worst part about this is that now there's an unused pipeline with no way to delete it.  This needs fixing.  Actually, anyone who is assigned as Tennent Admin should have visible access to everything without needed to be added to the object.  Tenent Admins need to be automatically added to every created object.

[azocc]

Thanks, but it's not possible to create a new pipeline and assign workspaces that are already part of another pipeline.  The workspace dropdown doesn't show workspaces already in another pipeline.  Also, I can't delete those workspaces from the unreachable pipelines.

The only other solution I can see is create new workspaces, republish objects, re-assign users and then create a enw pipeline with the new workspaces.

[v-menakakota]

Hi @azocc ,

You’re right. If the workspaces are already part of an existing pipeline, they won’t show up when creating a new one. And since the current pipeline is not accessible, you also can’t remove them from there.

In this case, the approach you mentioned creating new workspaces, republishing the content, and then setting up a new pipeline would work as a workaround.

Best Regards, 
Community Support Team

[v-menakakota]

Hi @azocc ,

Thanks for sharing the detailed information.

From what you described, it looks like the deployment pipeline was originally created by another admin, and since that person has left the organization, you’re currently unable to view or access the pipeline even though you have admin access to the workspaces. This can happen because deployment pipeline access is managed separately from workspace permissions.

Regarding the REST API, the admin pipelines API is not fully supported in the High Government environment, which is likely why the Invoke PowerBIRestMethod call is returning an error even though you are able to connect using PowerShell.

At the moment, if no existing pipeline admins are available, one possible approach is to have another tenant admin create a new deployment pipeline and reassign the workspaces to it.

Hope the above provided information help you resolve the issue, if you have any further concerns or queries, please feel free to reach out to us.

Best Regards, 
Community Support Team