agentleFS
PatrickGallucciPatrickGallucci/fabric-skills/skills/fabric-network-remediate/SKILL.md

fabric-network-remediate

Skill17 starsChanged 9 months agoMITView on GitHub

Diagnose and resolve Microsoft Fabric network performance issues including connectivity failures, latency, private endpoints, managed VNets, outbound access protection, gateway diagnostics, OneLake endpoint routing, service tag configuration, firewall allowlisting, DNS resolution, and Spark session startup delays. Use when remediate Fabric networking, slow Spark jobs, connection timeouts, private link errors, managed private endpoint approval, or capacity throttling.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the diagnostic script for automated assessment:

    line 45
  2. Distinctive:

    When Private Links or Managed VNets are enabled, Starter Pools are unavailable and Fabric must create clusters on demand, adding 2-5 …

    line 51
  3. Distinctive:

    If Pending or Failed, see private-endpoint-remediate.md

    line 57
  4. Distinctive:

    Run the automated validation:

    line 66
  5. Distinctive:

    When outbound access protection is enabled, public repositories (PyPI, Conda) are blocked.

    line 95
  6. Distinctive:

    When all Spark VCores are consumed, new jobs receive HTTP 430 errors.

    line 109
  7. Distinctive:

    Check current utilization in the Monitoring Hub

    line 111
  8. Distinctive:

    Consider upgrading capacity SKU if sustained

    line 113

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Microsoft Fabric Network Performance remediate

Systematic toolkit for diagnosing and resolving network performance issues across Microsoft Fabric workloads including Spark, OneLake, Data Warehouse, Pipelines, and Dataflows.

When to Use This Skill

  • Fabric Spark sessions take longer than expected to start (>10 seconds)
  • Connection timeouts to external data sources from notebooks or pipelines
  • Managed private endpoint status shows Pending or Failed
  • DNS resolution returns public IPs instead of private IPs
  • Outbound access protection blocks required dependencies (PyPI, Conda)
  • On-premises data gateway connectivity failures
  • OneLake API calls returning 403 or timeout errors
  • Capacity throttling errors (HTTP 430)
  • Dataflow Gen2 staging failures behind firewalls
  • Cross-workspace environment attachment failures due to network mismatch

Prerequisites

  • PowerShell 7+ with Az module installed (Install-Module Az -Scope CurrentUser)
  • Fabric Admin or Workspace Admin role for network configuration changes
  • Azure portal access for Private Link Service and DNS zone management
  • Network access to run nslookup, Test-NetConnection, and Resolve-DnsName

Step-by-Step Workflows

Workflow 1: Diagnose Spark Session Startup Delays

Spark startup times vary based on networking configuration. Consult the reference table:

ScenarioTypical Startup Time
Default settings, no libraries5-10 seconds
Default settings + library dependencies5-10 sec + 30 sec-5 min
High traffic in region, no libraries2-5 minutes
High traffic + library dependencies2-5 min + 30 sec-5 min
Network security (Private Links/VNet)2-5 minutes
Network security + library dependencies2-5 min + 30 sec-5 min

Run the diagnostic script for automated assessment:

.\scripts\Test-FabricNetworkHealth.ps1 -WorkspaceId "<workspace-id>" -CheckType SparkStartup

When Private Links or Managed VNets are enabled, Starter Pools are unavailable and Fabric must create clusters on demand, adding 2-5 minutes to session start time.

Workflow 2: Validate Managed Private Endpoint Connectivity

  1. Navigate to Fabric workspace Settings > Network security
  2. Under Managed private endpoints, verify Status shows Approved
  3. If Pending or Failed, see private-endpoint-remediate.md
  4. Validate DNS routing from a Fabric Notebook:
nslookup sqlserver.corp.contoso.com

Confirm the returned IP is a private range (10.x.x.x or 172.x.x.x), not public.

  1. Run the automated validation:
.\scripts\Test-FabricNetworkHealth.ps1 -WorkspaceId "<workspace-id>" -CheckType PrivateEndpoint

Workflow 3: Configure Firewall Allowlisting

Fabric requires specific endpoints and service tags. Run the firewall audit script:

.\scripts\Test-FabricNetworkHealth.ps1 -CheckType FirewallEndpoints

For the complete endpoint reference, see firewall-endpoints.md.

Key service tags for Azure Firewall / NSG rules:

TagPurposeDirection
Power BIFabric core servicesBoth
DataFactoryPipeline operationsBoth
PowerQueryOnlineDataflow processingBoth
SQLWarehouse connectivityOutbound
EventHubReal-Time AnalyticsOutbound
KustoAnalyticsReal-Time AnalyticsBoth

Workflow 4: Troubleshoot Outbound Access Protection

When outbound access protection is enabled, public repositories (PyPI, Conda) are blocked. To install libraries in secured environments:

  1. Prepare a requirements.txt on a machine with internet access
  2. Download packages and dependencies using pip:
pip download -r requirements.txt -d ./packages
  1. Upload packages as custom libraries in the Fabric Environment
  2. See outbound-access-guide.md for detailed steps

Workflow 5: Resolve Capacity Throttling (HTTP 430)

When all Spark VCores are consumed, new jobs receive HTTP 430 errors. Formula: 1 Capacity Unit = 2 Spark VCores.

  1. Check current utilization in the Monitoring Hub
  2. Cancel idle or stuck Spark sessions
  3. Consider upgrading capacity SKU if sustained
  4. Enable queueing for pipeline and Spark Job Definition workloads

For queue limits by SKU, see capacity-throttling.md.

remediate Quick Reference

SymptomLikely CauseFirst Action
Spark startup >2 minPrivate Link/VNet enabledExpected; Starter Pools unavailable
Connection timeout from SparkFirewall blocking Fabric subnetOpen required ports (1433 for SQL)
DNS resolves to public IPPrivate DNS zone not linkedAdd A record pointing to private IP
MPE status = FailedPLS rejected or deletedRe-create MPE, verify PLS exists
HTTP 430 errorCapacity VCores exhaustedCancel jobs or upgrade SKU
PyPI install blockedOutbound access protectionUpload packages as custom libraries
Cross-workspace env failsNetwork settings mismatchEnsure same capacity and network config
OneLake API 403Endpoint URL validationUse *.dfs.fabric.microsoft.com

References

  • Private Endpoint remediate
  • Firewall Endpoints and Allowlist
  • Outbound Access Protection Guide
  • Capacity Throttling and Queue Limits
  • Diagnostic Report Template

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.