# Get started: your first governed Role Assistant
Outcome: by the end of this path, one business role has a tested, governed Role Assistant — running on a certified connected system, reachable in a conversation channel, with evidence an operator can review.
This section is the shortest supported path to that outcome. It is not a product tour, and it does not cover enterprise scale, Track B configure depth, or the operating-model detail that lives in Adopt — those come after the first Role Assistant works.
The path
| # | Step | Where |
|---|---|---|
| 1 | Deploy from Azure Marketplace | Azure Marketplace installation |
| 2 | Activate the tenant | Tenant activation wizard |
| 3 | Complete the first session | First session checklist |
| 4 | Know what Azure created | Azure services created |
| 5 | Describe the first business requirement | Deep link — Business Transformation Assistant (Role Assistants) |
| 6 | Establish or connect the first governed system | Deep link — Create a Connected System (Build) |
| 7 | Turn that certified system into a Role Assistant | From integrations to Role Assistant, Operate your first Role Assistant |
| 8 | Connect an assistant channel | Connect assistant channels |
| 9 | Test governed behavior | Deep link — Test Role Assistants (Build) |
Steps 1–4 and 7–8 are owned and taught in this section. Steps 5, 6, and 9 are deep links — the Business Transformation Assistant, connected-system setup, and Role Assistant test procedure each already have a canonical home, and Get Started does not duplicate them.
Who does what
| Role | Focus |
|---|---|
| Cloud / procurement | Marketplace purchase and deploy |
| Platform admin | Wizard completion, first session, catalogs, channel activation |
| Business sponsor | Describes the first requirement (Business Transformation Assistant); needs the outcome, not the runbook |
| Integrator | Establishes the first governed system in Build after tenant ACTIVE; certifies it here in steps 7–8 |
Example
An enterprise deploys AI Fabrix in Azure West Europe, completes tenant activation with Entra ID, confirms tenant ACTIVE, and assigns an integration developer role. A business sponsor describes wanting faster contract-exception handling to the Business Transformation Assistant, which points to a CRM and a document store as the first governed system. The integrator establishes that system with the quickstart external system path, certifies it, and the platform admin makes the resulting Role Assistant available in a Teams channel.
Business value
A single documented path from tenant to first governed Role Assistant reduces failed pilots, security gaps from skipped identity steps, and confusion about when Business Transformation Assistant, Build, and channel activation each apply.
Where to go next
- Scale beyond the first Role Assistant — Adopt covers the operating model, adoption roadmap, and zero-enterprise onboarding.
- More connected systems — Build covers certification, publishing, and channel install how-tos in depth.
- Platform sizing and control boundaries — Platform sizing and environments.
Limits
Detailed Azure parameter names, internal resource topology, and CLI commands vary by version — use the linked configure guides for step-by-step actions. This page is a map, not a runbook.