Assessment
Assessment answers what exists, what it needs, and where it could fit. It is not deployment, remediation, or migration.
SQL Server starting points
Section titled “SQL Server starting points”The first supported routes will be SQL Server enabled by Azure Arc and the migration component in SQL Server Management Studio.
These routes provide different evidence and must remain separate in the plan:
| Capability | Purpose | Important planning detail |
|---|---|---|
| Arc inventory | Discover connected SQL Server instances and metadata | Requires Arc onboarding, extension health, identity, network, and data-governance review |
| Arc best-practices assessment | Find configuration and operational recommendations | Has its own extension, Log Analytics, role, SQL permission, connectivity, collection, and cost prerequisites |
| Arc migration assessment | Assess Azure SQL readiness, sizing, risks, and target options | Requires a supported connected Windows instance and extension; published retail estimates use documented assumptions |
| SSMS migration component | Run a local metadata-based readiness assessment or view Arc results | Requires a supported SSMS version and SQL permissions; local and Arc-backed results differ |
The toolkit will identify which capability is requested, validate its prerequisites, and report missing evidence. It will not silently enable agents, workspaces, recurring collection, or billing.
Privilege and collection disclosure
Section titled “Privilege and collection disclosure”Microsoft documents that the Azure SQL extension performs Arc migration-assessment collection as NT AUTHORITY\SYSTEM by default. Microsoft also documents a least-privilege service-account alternative.
Before enabling collection, the plan must show:
- the operating-system and SQL identity used;
- Azure roles and SQL permissions;
- extension, agent, workspace, and network prerequisites;
- metadata and performance data collected, destination, schedule, and retention;
- licensing and billing implications, including Arc-enabled SQL Server billing choices;
- how collection is disabled and its artifacts are removed.
Using SYSTEM cannot be hidden behind a default. The user must see the privilege difference and choose the documented route that fits the environment.
Assessment result
Section titled “Assessment result”The normalized result will keep these dimensions separate:
- inventory and evidence freshness;
- compatibility and feature blockers;
- workload shape, sizing, availability, and recovery needs;
- identity, network, encryption, sensitive-data, and compliance constraints;
- target options and their trade-offs;
- licensing and cost assumptions;
- migration readiness and required remediation;
- confidence and unresolved questions.
Assessment can inform a later migration decision, but it does not move data or prove that a target is fit for production.
Fabric and FUAM
Section titled “Fabric and FUAM”Fabric assessment will validate tenant, capacity, workspace, item, security, and lifecycle prerequisites. When Fabric Unified Admin Monitoring is detected, the toolkit will validate the existing installation and preserve it by default. Setup or repair requires a user-reviewed summary and explicit confirmation.