Hey @sreenivasulub ,
If the Power BI REST API recently stopped allowing you to filter by capacity in the request itself, this change cannot be reverted from your side. Microsoft periodically updates and standardizes the Admin REST APIs, and when parameters are deprecated or removed, tenants must adapt to the new supported behavior. There is no setting in the tenant or capacity configuration that allows you to restore the previous filtering option.
The correct approach now is to retrieve the full dataset from the Admin endpoint and apply filtering in your own solution layer. For example, first call the capacities endpoint to retrieve the list of capacity IDs that belong to SKT:
GET https://api.powerbi.com/v1.0/myorg/admin/capacities
Then retrieve all workspaces including their capacity information:
GET https://api.powerbi.com/v1.0/myorg/admin/groups?$expand=capacity
From there, filter the workspaces locally by keeping only those where the workspace capacityId matches one of your SKT capacity IDs. If you are consuming usage data through the activity events endpoint:
GET https://api.powerbi.com/v1.0/myorg/admin/activityevents?startDateTime=2026-02-24T00:00:00&endDateTime=2026-02-24T23:59:59
you should join the returned WorkspaceId to your filtered workspace list and restrict the results to only the capacities relevant to SKT. This design ensures you remain compliant with the current API behavior and makes your solution more robust against future changes.
From an enterprise architecture perspective, it is not recommended to rely on server-side filtering in Admin APIs for tenant segmentation. Instead, maintain your own registry of approved capacity IDs or workspace IDs and apply filtering within your data pipeline or Power BI model. This approach is more stable, scalable, and future-proof.
If this explanation helped, please mark it as the solution so others can find it easily.
If it helped, a quick Kudos is always appreciated it highlights useful answers for the community.
Thanks for being part of the discussion!
