fabric-rest-api-perf-remediatelisted

# Microsoft Fabric REST API Performance remediate Structured diagnostic workflows and automation scripts for identifying and resolving performance bottlenecks in Microsoft Fabric REST API integrations. ## When to Use This Skill - API calls to `api.fabric.microsoft.com` are slow or timing out - Receiving HTTP 429 (Too Many Requests) responses with Retry-After headers - Long running operations (LRO) polling is inefficient or stalling - Paginated API responses are taking too long to enumerate - Bulk workspace or item operations exceed capacity throttle limits - Entra ID token acquisition is adding unexpected latency - Spark job submissions return HTTP 430 (TooManyRequestsForCapacity) - Need to benchmark Fabric REST API throughput for a given capacity SKU ## Prerequisites - PowerShell 7+ with `Invoke-RestMethod` support - Microsoft Entra ID app registration with appropriate Fabric scopes - A valid Bearer token or MSAL-based authentication flow - Access to at least one Fabric workspace ## Diagnostic Decision Tree Determine the root cause category before applying a fix: ``` API Call Slow or Failing? ├── HTTP 429 returned? │ ├── YES → Throttling. See §1 Throttling Diagnosis │ └── NO → Continue ├── HTTP 430 returned? │ ├── YES → Capacity exhausted. See §2 Capacity Limits │ └── NO → Continue ├── HTTP 202 + LRO stalling? │ ├── YES → Polling issue. See §3 LRO Optimization │ └── NO → Continue ├── Large result sets slow? │ ├── YES → Pagination. See §4 Pagination T