updating freshness'

Author: barclayn

articles/active-directory/enterprise-users/media/users-restrict-guest-permissions/external-collaboration-settings.png

@@ -4,7 +4,7 @@ description: List of services supporting managed identities
 services: active-directory
 author: barclayn
 ms.author: barclayn
-ms.date: 01/10/2022
+ms.date: 05/25/2023
 ms.topic: conceptual
 ms.service: active-directory
 ms.subservice: msi

articles/active-directory/managed-identities-azure-resources/managed-identities-status.md

@@ -12,7 +12,7 @@ ms.subservice: msi
 ms.topic: tutorial
 ms.tgt_pltfrm: na
 ms.workload: identity
-ms.date: 02/18/2022
+ms.date: 05/25/2023
 ms.author: barclayn
 ms.collection: M365-identity-device-management
 #Customer intent: As a developer or administrator I want to configure a Windows virtual machine to retrieve a secret from key vault using a managed identity and have a simple way to validate my configuration before using it for development

articles/active-directory/managed-identities-azure-resources/tutorial-windows-vm-access-nonaad.md

@@ -11,13 +11,12 @@ ms.subservice: msi
 ms.topic: tutorial
 ms.tgt_pltfrm: na
 ms.workload: identity
-ms.date: 01/11/2022
+ms.date: 05/25/2023
 ms.author: barclayn
 ms.collection: M365-identity-device-management
 ---
 # Tutorial: Use a Windows VM system-assigned managed identity to access Azure SQL
 
-[!INCLUDE [preview-notice](../../../includes/active-directory-msi-preview-notice.md)]
 
 This tutorial shows you how to use a system-assigned identity for a Windows virtual machine (VM) to access Azure SQL Database. Managed Service Identities are automatically managed by Azure and enable you to authenticate to services that support Azure AD authentication, without needing to insert credentials into your code. You learn how to:
 
@@ -50,20 +49,21 @@ There are two steps to granting your VM access to a database:
 **To [configure Azure AD authentication](/azure/azure-sql/database/authentication-aad-configure):**
 
 1. In the Azure portal, select **SQL servers** from the left-hand navigation.
-2. Click the SQL server to be enabled for Azure AD authentication.
+2. Select the SQL server to be enabled for Azure AD authentication.
 3. In the **Settings** section of the blade, click **Active Directory admin**.
 4. In the command bar, click **Set admin**.
 5. Select an Azure AD user account to be made an administrator of the server, and click **Select.**
 6. In the command bar, click **Save.**
 
+
 ### Create contained user
 
 This section shows how to create a contained user in the database that represents the VM's system assigned identity. For this step, you need [Microsoft SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms) (SSMS). Before beginning, it may also be helpful to review the following articles for background on Azure AD integration:
 
 - [Universal Authentication with SQL Database and Azure Synapse Analytics (SSMS support for MFA)](/azure/azure-sql/database/authentication-mfa-ssms-overview)
 - [Configure and manage Azure Active Directory authentication with SQL Database or Azure Synapse Analytics](/azure/azure-sql/database/authentication-aad-configure)
 
-SQL DB requires unique Azure AD display names. With this, the Azure AD accounts such as users, groups and Service Principals (applications), and VM names enabled for managed identity must be uniquely defined in Azure AD regarding their display names. SQL DB checks the Azure AD display name during T-SQL creation of such users and if it is not unique, the command fails requesting to provide a unique Azure AD display name for a given account.
+SQL DB requires unique Azure AD display names. With this, the Azure AD accounts such as users, groups and Service Principals (applications), and VM names enabled for managed identity must be uniquely defined in Azure AD regarding their display names. SQL DB checks the Azure AD display name during T-SQL creation of such users and if it isn't unique, the command fails requesting to provide a unique Azure AD display name for a given account.
 
 **To create a contained user:**
 
@@ -75,7 +75,7 @@ SQL DB requires unique Azure AD display names. With this, the Azure AD accounts
 6. In the **Connect to database** field, enter the name of the non-system database you want to configure.
 7. Click **Connect**. Complete the sign-in process.
 8. In the **Object Explorer**, expand the **Databases** folder.
-9. Right-click on a user database and click **New query**.
+9. Right-click on a user database and select **New query**.
 10. In the query window, enter the following line, and click **Execute** in the toolbar:
 
     > [!NOTE]
@@ -89,7 +89,7 @@ SQL DB requires unique Azure AD display names. With this, the Azure AD accounts
 11. Clear the query window, enter the following line, and click **Execute** in the toolbar:
 
     > [!NOTE]
-    > `VMName` in the following command is the name of the VM that you enabled system assigned identity on in the prerequsites section.
+    > `VMName` in the following command is the name of the VM that you enabled system assigned identity on in the prerequisites section.
 
     ```sql
     ALTER ROLE db_datareader ADD MEMBER [VMName]