Use this page as the canonical reference for the current private-beta Microsoft commercial activation path, buyer onboarding flow, and extension-track posture for AppSource/Azure Marketplace.
https://decionis.com/marketplace/microsoft/azure-signonhttps://commerce.decionis.com/platforms/microsoft/landinghttps://api.decionis.com/v1/platforms/microsoft/events3d7923b6-91d6-45e9-996d-a7f18e7f2ca0api://decionis.com/3d7923b6-91d6-45e9-996d-a7f18e7f2ca04e6e163e-59dc-4070-b474-376a2c5fbfc8One Microsoft lifecycle serves every Decionis Microsoft offer. Extension workloads are separate tracks.
Every Microsoft offer runs through one lifecycle in Decionis Commerce: your landing-page token is resolved, the exact plan you bought is activated, and each subscription change from Microsoft is recorded.
After purchase you sign in with your Decionis account, and your workspace opens or is created for that plan with no manual setup step.
The Teams finance tab exchanges native Teams SSO for Microsoft Graph and reads the signed-in user plus workspace metadata when tenant consent and secret configuration are present.
Power Automate finance workflows can call a shipped Decionis policy-check endpoint and register webhook triggers through the published connector spec before executing or resuming an action.
The shipped Teams package installs to a team by default: a team-scoped governance tab and a registered bot that posts auto-escalated actions into the team channel as interactive Approve/Reject cards. Channel routing binds automatically when Decionis is added to a channel, and gate-time escalations fan out a card with a signed Decision Dossier. The capability stays partial only until Microsoft completes bot/team-scope validation in the target tenant. SharePoint Framework remains a separate planned workload.
The Dataverse managed-solution package, Business Central AL add-on, and shared Microsoft event gateway are implemented locally. Clean-tenant installation and Microsoft certification remain release gates.
Entra-protected Event Grid delivery, a Service Bus subscriber worker, narrow-scope Bicep templates, schema admission, replay, and disconnect are implemented. Production tenant and load validation remain release gates.
Finance and Operations business-event normalization and Azure transport paths are implemented. Exact catalog identifiers and payload fixtures must still be captured from each target release before public support claims.
Security evidence export is supported; direct productized Microsoft Security service integrations are tracked as a later workload.