Microsoft Fabric VS Code extension blocking extension ID

Question

The Microsoft Fabric VS Code extension documents itself as the core extension and exposes @microsoft/vscode-fabric-api for core/satellite integration. We developed an internal satellite extension against that API, but registration is rejected because our VS Code extension ID is not in the core extension's trusted extension list.

Is third-party/internal-enterprise development of Fabric satellite extensions supported?

If so, what is the supported mechanism for registering or approving an external extension ID as trusted?

If not, is the published satellite-extension API currently intended only for Microsoft-authored Fabric extensions?

Answer 1

Hi @Dan Davis ,

Thank you for sharing the registration details. Based on the behavior described, your extension reaches the Fabric core extension, but registration is rejected because its extension ID is not included in the trusted extension list.

Microsoft documents the Microsoft Fabric VS Code extension as the core extension used by other Fabric extensions, and lists Fabric User Data Functions as a related Fabric extension. The published guidance, however, does not define a customer-configurable trusted list or an external publisher registration workflow.

Since this concerns the satellite trust model and third-party extensibility, we recommend opening an issue or discussion in the public Microsoft Fabric VS Code repository

Please ask the repository maintainers to confirm whether an external trust-enrollment process is available or whether third-party satellite extension support is planned.

If this integration is required for a production workload or you need formal case tracking, please also submit a Microsoft Fabric support request through this Microsoft Support Guide if you have the required permissions, license, and support plan.

Until this is confirmed, the current integration should not be considered a documented supported scenario.

If you found my response helpful or informative, I would greatly appreciate it if you could follow this guide for your confirmation.

Thank you.

Answer 2

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