Some Microsoft Fabric features reach general availability without the deployment, automation, or diagnostic capabilities teams need for production. What would a useful minimum readiness standard look like?
What should a Fabric feature have before it's called generally available?
Answers
Start with a release checklist that covers the whole lifecycle, not just whether the feature works in the portal. Can its configuration be stored in source control, deployed reproducibly through CI/CD, and managed through APIs or other automation? Can a team diagnose a failure without guessing?
Add documented security and identity behavior, complete documentation, and production-readiness testing. If something on the checklist isn't supported, spell out the limitation clearly rather than leaving teams to discover it during deployment.
Reply to this answer
Security and identity deserve their own gate. A feature can be technically available and still be unusable in an environment that relies on Entra integration and consistent access controls.
Document which identities are supported, how permissions are managed, and where the gaps are. Bespoke identity behavior for individual objects makes it harder to assess and operate the whole environment.
Reply to this answer
I'd still assess each feature before adopting it, even if Microsoft publishes a stronger GA standard. The label doesn't tell you whether the specific source control, identity, deployment, and troubleshooting capabilities your team needs are there.
Check the documented limitations against your own deployment process and test a reproducible rollout before relying on the feature in production. Different teams will have different blockers.
Reply to this answer
There's a tension here. A vendor may want broader usage before deciding how much further to develop a feature, while customers may avoid previews for production work. That doesn't make a GA label a substitute for being usable, though.
If full enterprise support isn't ready, clearer documentation of exactly what's missing would at least let teams make an informed choice.
Reply to this answer
For the feedback portal itself, try pasting the proposal as plain text or switching to plain text mode first. The editor can add styled tags that the publishing validator rejects, so removing the formatting may get the submission through.
Reply to this answer
Add your answer
Answers are reviewed before publication.
n.395+pluvdari:
API parity should cover the operations needed to manage the feature, not just creating it. Otherwise a deployment can still depend on manual steps.