Microsoft Fabric VS Code extension blocking extension ID

There is currently no publicly documented or supported mechanism for an internal or third-party extension ID to be added to the Microsoft Fabric VS Code extension’s trusted satellite list.

The published documentation describes the Microsoft Fabric extension as the core extension that enables other Fabric extensions, but it documents only Microsoft’s Fabric extensions and does not provide an external registration, manifest declaration, tenant setting, or approval workflow for satellite developers.^1^

The public repository likewise presents the core/satellite architecture, but no public onboarding or trust-enrollment contract is documented for external publishers.^2^ The production core extension is published under Microsoft’s fabric publisher identity.^3^

Practical conclusion

• Treat @microsoft/vscode-fabric-api as an implementation API for the current Microsoft Fabric extension ecosystem, not as a generally supported third-party extensibility API.
• A package being accessible or exported does not itself establish a supported external contract.
• There is no documented customer-side configuration that can approve an extension ID.
• VS Code publisher verification, enterprise extension allowlisting, and Fabric tenant permissions would not add an ID to the Fabric core extension’s own trust list.

Do not work around the check by patching the installed extension, changing your extension ID to imitate a trusted publisher, or modifying packaged files. Those approaches would be unsupported and would not provide a stable deployment path.

Requesting official enablement

Use the public Fabric extension repository to open an issue or discussion requesting third-party satellite support.^2^ Include:

1. Your extension ID and publisher model—private VSIX, private marketplace, or public Marketplace.
2. The Fabric item types and API operations required.
3. The exact rejection message and relevant Output channel logs.
4. The versions of VS Code, fabric.vscode-fabric, and @microsoft/vscode-fabric-api.
5. Whether the extension is intended for one tenant or general distribution.
6. A request for confirmation of either:
   • an external trust-enrollment process, or
   • a supported public extensibility roadmap.

Until Microsoft provides that approval path or explicitly adds the extension ID, an internal satellite cannot be considered a supported integration. For current production work, use documented Fabric interfaces—such as Fabric REST APIs or item-definition workflows—outside the trusted satellite registration path where they satisfy the scenario.^1^

References

1. Microsoft Fabric extensions for Visual Studio Code
2. GitHub - microsoft/vscode-fabric: Microsoft Fabric extension for VS Code
3. Microsoft Fabric - Visual Studio Marketplace