A Microsoft tool designed to automate database migration to SQL Server from Access, DB2, MySQL, Oracle, and SAP ASE.
The Azure extension for SQL Server is optional and independent of Azure Arc configuration. The failure during the SQL Server 2025 upgrade only indicates that the Azure extension component (“Azure Arc onboard”) could not be installed or upgraded; it does not prevent using SQL Server 2025 itself.
Key points:
- Why “Azure Arc onboard” appears
- The Azure extension for SQL Server is the component that enables “SQL Server enabled by Azure Arc” capabilities (inventory, governance, billing, etc.).
- Setup tries to install/upgrade this extension so the instance can be Arc‑enabled later, even if the server is not currently connected to Azure Arc.
- The reference to “Azure Arc onboard” does not mean the machine is already Arc‑enabled; it is just the name of the extension component.
- Azure Arc vs. Azure extension
- Azure Arc–enabling a server is a separate step that connects the machine to Azure.
- The Azure extension for SQL Server can be installed either:
- By connecting the server to Azure Arc, or
- From the SQL Server command line setup.
- Not having Azure Arc configured in the subscription does not mean the Azure extension can never be used; it only means Arc features will not function until the server is onboarded.
- What the error means for the current installation
- SQL Server 2025 engine upgrade completed; only the Azure extension feature failed.
- You can run SQL Server normally without the Azure extension.
- If desired, the Azure extension can be installed or repaired later, independently of the SQL Server engine.
- How to remediate if Azure extension is needed
- First confirm the SQL Server engine is healthy and running.
- If the extension is needed:
- Use the Azure portal or CLI to verify whether the machine is (or will be) Arc‑enabled.
- Install or repair the Azure extension for SQL Server using one of the supported methods:
- Connect the server to Azure Arc (auto‑onboarding installs the extension by default).
- Install from the SQL Server command line as described in “Install Azure extension for SQL Server from the command line”.
- If the extension still fails or appears unhealthy, use the Azure portal health dashboard or Azure Resource Graph to inspect
FailureReasons,RecommendedAction, andLastExtensionStatusMessage, then follow the recommended troubleshooting steps.
- If the extension remains failed/unhealthy
- Use the built‑in extension health dashboard in the Azure portal to identify the extension state and recommended actions.
- If provisioning repeatedly fails, uninstall the extension and reinstall it via portal/CLI, and if needed, check deployer/extension logs as described in the troubleshooting guidance.
In summary, the error does not block SQL Server 2025 usage and does not mean Azure extensions can never be used. It only means the Azure extension component did not complete successfully during this upgrade; it can be installed or fixed later when Azure Arc/extension functionality is actually required.
References: