You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/windows/sql/virtual-machines-windows-sql-register-with-resource-provider.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -333,15 +333,15 @@ Yes. Upgrading the manageability mode from lightweight to full is supported via
333
333
334
334
No. Downgrading the SQL Server IaaS extension manageability mode is not supported. The manageability mode can't be downgraded from full mode to lightweight or no-agent mode, and it can't be downgraded from lightweight mode to no-agent mode.
335
335
336
-
To change the manageability mode from full manageability, remove the SQL Server IaaS extension. Then, drop the Micorsoft.SqlVirtualMachine resource and re-register the SQL Server VM with the SQL VM resource provider.
336
+
To change the manageability mode from full manageability, remove the SQL Server IaaS extension. Then, drop the Microsoft.SqlVirtualMachine resource and re-register the SQL Server VM with the SQL VM resource provider.
337
337
338
338
**Can I register with the SQL VM resource provider from the Azure portal?**
339
339
340
340
No. Registering with the SQL VM resource provider is not available in the Azure portal. Registering with the SQL VM resource provider in full manageability mode is supported with the Azure CLI or PowerShell. Registering with the SQL VM resource provider in lightweight or no-agent manageability mode is supported only by Azure PowerShell APIs.
341
341
342
342
**Can I register a VM with the SQL VM resource provider before SQL Server is installed?**
343
343
344
-
No. A VM should have at least one SQL Server instance to successfully register with the SQL VM resource provider. If there is no SQL Server instance on the VM, the new Micosoft.SqlVirtualMachine resource will be in a failed state.
344
+
No. A VM should have at least one SQL Server instance to successfully register with the SQL VM resource provider. If there is no SQL Server instance on the VM, the new Microsoft.SqlVirtualMachine resource will be in a failed state.
345
345
346
346
**Can I register a VM with the SQL VM resource provider if there are multiple SQL Server instances?**
347
347
@@ -362,4 +362,4 @@ For more information, see the following articles:
362
362
*[Overview of SQL Server on a Windows VM](virtual-machines-windows-sql-server-iaas-overview.md)
363
363
*[FAQ for SQL Server on a Windows VM](virtual-machines-windows-sql-server-iaas-faq.md)
364
364
*[Pricing guidance for SQL Server on a Windows VM](virtual-machines-windows-sql-server-pricing-guidance.md)
365
-
*[Release notes for SQL Server on a Windows VM](virtual-machines-windows-sql-server-iaas-release-notes.md)
365
+
*[Release notes for SQL Server on a Windows VM](virtual-machines-windows-sql-server-iaas-release-notes.md)
0 commit comments