Individual skill

fabric-network-remediate

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.

skills/fabric-network-remediate/SKILL.md

Read pinned source

Source commit cee03dc1199cd2a9765b439fa41930d480e5989d

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
17
Repository last updated
Jun 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# 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
Back to top