From 99366104f872964b3eb335931de1c737c02025ce Mon Sep 17 00:00:00 2001 From: Pedro Lopes Date: Mon, 8 Jul 2019 16:39:20 -0700 Subject: [PATCH] Update registry.md --- samples/manage/sql-server-extended-security-updates/registry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/samples/manage/sql-server-extended-security-updates/registry.md b/samples/manage/sql-server-extended-security-updates/registry.md index a6f3c575..29f70a65 100644 --- a/samples/manage/sql-server-extended-security-updates/registry.md +++ b/samples/manage/sql-server-extended-security-updates/registry.md @@ -6,7 +6,7 @@ Before being able access the Extended Security Updates (ESU) download area in th **Important**: It's not required to register a SQL Server instance for ESUs when running an Azure Virtual Machine that is configured for Automatic Updates. For more information, see [Manage Windows updates by using Azure Automation](https://docs.microsoft.com/azure/automation/automation-tutorial-update-management). ## Prepare to register SQL Server instances -To register SQL Server instances, you must first create a SQL Server Registry in the [Azure portal](https://portal.azure.com). +To register SQL Server instances, you must first create a SQL Server Registry in the [Azure portal](https://portal.azure.com/#create/Microsoft.SqlServerRegistration). **Note**: This operation only needs to be done once. After a SQL Server Registry is created, it can be used to register multiple SQL Server instances.