Merge pull request #216914 from MicrosoftDocs/main

11/02 AM Publish

Author: huypub

.openpublishing.redirection.json

@@ -6423,11 +6423,6 @@
             "redirect_url": "/azure/storage/blobs/storage-encrypt-decrypt-blobs-key-vault",
             "redirect_document_id": false
         },
-        {
-            "source_path_from_root": "/articles/storage/blobs/storage-encrypt-decrypt-blobs-key-vault.md",
-            "redirect_url": "/azure/storage/blobs/client-side-encryption",
-            "redirect_document_id": false
-        },
         {
             "source_path_from_root": "/articles/storage/blobs/Storage-blob-performance-tiers.md",
             "redirect_url": "/azure/storage/common/storage-account-overview",

articles/active-directory/authentication/howto-authentication-temporary-access-pass.md

@@ -142,10 +142,15 @@ Users managing their security information at [https://aka.ms/mysecurityinfo](htt
 ![Screenshot of how users can manage a Temporary Access Pass in My Security Info.](./media/how-to-authentication-temporary-access-pass/tap-my-security-info.png)
 
 ### Windows device setup
-Users with a Temporary Access Pass can navigate the setup process on Windows 10 and 11 to perform device join operations and configure Windows Hello For Business. Temporary Access Pass usage for setting up Windows Hello for Business varies based on the devices joined state: 
-- During Azure AD Join setup, users can authenticate with a TAP (no password required) and setup Windows Hello for Business.
-- On already Azure AD Joined devices, users must first authenticate with another method such as a password, smartcard or FIDO2 key, before using TAP to set up Windows Hello for Business. 
-- On Hybrid Azure AD Joined devices, users must first authenticate with another method such as a password, smartcard or FIDO2 key, before using TAP to set up Windows Hello for Business. 
+Users with a Temporary Access Pass can navigate the setup process on Windows 10 and 11 to perform device join operations and configure Windows Hello for Business. Temporary Access Pass usage for setting up Windows Hello for Business varies based on the devices joined state. 
+
+For Azure AD Joined devices: 
+- During the Azure AD Join setup process, users can authenticate with a TAP (no password required) to join the device and register Windows Hello for Business.
+- On already joined devices, users must first authenticate with another method such as a password, smartcard or FIDO2 key, before using TAP to set up Windows Hello for Business. 
+- If the [Web sign-in](https://learn.microsoft.com/windows/client-management/mdm/policy-csp-authentication#authentication-enablewebsignin) feature on Windows is also enabled, the user can use TAP to sign into the device. This is intended only for completing initial device setup, or recovery when the user does not know or have a password. 
+
+For Hybrid Azure AD Joined devices: 
+- Users must first authenticate with another method such as a password, smartcard or FIDO2 key, before using TAP to set up Windows Hello for Business. 
 
 ![Screenshot of how to enter Temporary Access Pass when setting up Windows 10.](./media/how-to-authentication-temporary-access-pass/windows-10-tap.png)
 

articles/active-directory/develop/active-directory-how-applications-are-added.md

@@ -9,10 +9,10 @@ ms.service: active-directory
 ms.subservice: develop
 ms.topic: reference
 ms.workload: identity
-ms.date: 03/30/2021
+ms.date: 10/28/2022
 ms.author: cwerner
 ms.reviewer: jmprieur, saeeda
-ms.custom: aaddev
+ms.custom: aaddev, engagement-fy23
 # Customer intent: As a developer, I want to know whether there's a Microsoft Authentication Library (MSAL) available for the language/framework I'm using to build my application, and whether the library is GA or in preview.
 ---
 

articles/active-directory/develop/reference-v2-libraries.md

@@ -0,0 +1,87 @@
+---
+title: Convert local guests into Azure AD B2B guest accounts
+description: Learn how to convert local guests into Azure AD B2B guest accounts 
+services: active-directory 
+author: gargi-sinha
+ms.author: gasinh
+manager: martinco
+ms.date: 11/03/2022
+ms.topic: how-to
+ms.service: active-directory
+ms.subservice: enterprise-users
+ms.workload: identity
+ms.custom: it-pro
+ms.collection: M365-identity-device-management
+---
+
+# Convert local guests into Azure Active Directory B2B guest accounts
+
+Azure Active Directory (Azure AD B2B) allows external users to collaborate using their own identities. However, it isn't uncommon for organizations to issue local usernames and passwords to external users. This approach isn't recommended as the bring-your-own-identity (BYOI) capabilities provided
+by Azure AD B2B to provide better security, lower cost, and reduce
+complexity when compared to local account creation. Learn more
+[here.](https://learn.microsoft.com/azure/active-directory/fundamentals/secure-external-access-resources)
+
+If your organization currently issues local credentials that external users have to manage and would like to migrate to using Azure AD B2B instead, this document provides a guide to make the transition as seamlessly as possible.
+
+## Identify external-facing applications
+
+Before migrating local accounts to Azure AD B2B, admins should understand what applications and workloads these external users need to access. For example, if external users need access to an application that is hosted on-premises, admins will need to validate that the application is integrated with Azure AD and that a provisioning process is implemented to provision the user from Azure AD to the application.
+The existence and use of on-premises applications could be a reason why local accounts are created in the first place. Learn more about
+[provisioning B2B guests to on-premises
+applications.](https://learn.microsoft.com/azure/active-directory/external-identities/hybrid-cloud-to-on-premises)
+
+All external-facing applications should have single-sign on (SSO) and provisioning integrated with Azure AD for the best end user experience.
+
+## Identify local guest accounts
+
+Admins will need to identify which accounts should be migrated to Azure AD B2B. External identities in Active Directory should be easily identifiable, which can be done with an attribute-value pair. For example, making ExtensionAttribute15 = `External` for all external users. If these users are being provisioned via Azure AD Connect or Cloud Sync, admins can optionally configure these synced external users
+to have the `UserType` attributes set to `Guest`. If these users are being
+provisioned as cloud-only accounts, admins can directly modify the
+users' attributes. What is most important is being able to identify the
+users who you want to convert to B2B.
+
+## Map local guest accounts to external identities
+
+Once you've identified which external user accounts you want to
+convert to Azure AD B2B, you need to identify the BYOI identities or external emails for each user. For example, admins will need to identify that the local account ([email protected]) is a user whose home identity/email address is [email protected]. How to identify the home identities is up to the organization, but some examples include:
+
+- Asking the external user's sponsor to provide the information.
+
+- Asking the external user to provide the information.
+
+- Referring to an internal database if this information is already known and stored by the organization.
+
+Once the mapping of each external local account to the BYOI identity is done, admins will need to add the external identity/email to the user.mail attribute on each local account.
+
+## End user communications
+
+External users should be notified that the migration will be taking place and when it will happen. Ensure you communicate the expectation that external users will stop using their existing password and post-migration will authenticate with their own home/corporate credentials going forward. Communications can include email campaigns, posters, and announcements.
+
+## Migrate local guest accounts to Azure AD B2B
+
+Once the local accounts have their user.mail attributes populated with the external identity/email that they're mapped to, admins can [convert the local accounts to Azure AD B2B by inviting the local account.](https://learn.microsoft.com/azure/active-directory/external-identities/invite-internal-users)
+This can be done in the UX or programmatically via PowerShell or the Microsoft Graph API. Once complete, the users will no longer
+authenticate with their local password, but will instead authenticate with their home identity/email that was populated in the user.mail attribute. You've successfully migrated to Azure AD B2B.
+
+## Post-migration considerations
+
+If local accounts for external users were being synced from on-premises, admins should take steps to reduce their on-premises footprint and use cloud-native B2B guest accounts moving forward. Some possible actions can include:
+
+- Transition existing local accounts for external users to Azure AD B2B and stop creating local accounts. Post-migration, admins should invite external users natively in Azure AD.
+
+- Randomize the passwords of existing local accounts for external users to ensure they can't authenticate locally to on-premises resources. This will increase security by ensuring that authentication and user lifecycle is tied to the external user's home identity.
+
+## Next steps
+
+See the following articles on securing external access to resources. We recommend you take the actions in the listed order.
+
+1. [Determine your desired security posture for external access](1-secure-access-posture.md)
+1. [Discover your current state](2-secure-access-current-state.md)
+1. [Create a governance plan](3-secure-access-plan.md)
+1. [Use groups for security](4-secure-access-groups.md)
+1. [Transition to Azure AD B2B](5-secure-access-b2b.md)
+1. [Secure access with Entitlement Management](6-secure-access-entitlement-managment.md)
+1. [Secure access with Conditional Access policies](7-secure-access-conditional-access.md) 
+1. [Secure access with Sensitivity labels](8-secure-access-sensitivity-labels.md)
+1. [Secure access to Microsoft Teams, OneDrive, and SharePoint](9-secure-access-teams-sharepoint.md)
+1. [Secure local guest accounts](10-secure-local-guest.md) (You’re here)

articles/active-directory/fundamentals/10-secure-local-guest.md

@@ -8,7 +8,7 @@ ms.service: active-directory
 ms.workload: identity
 ms.subservice: fundamentals
 ms.topic: conceptual
-ms.date: 09/13/2022
+ms.date: 11/03/2022
 ms.author: gasinh
 ms.reviewer: ajburnle
 ms.custom: "it-pro, seodec18"
@@ -89,3 +89,5 @@ See the following articles on securing external access to resources. We recommen
 8. [Secure access with Sensitivity labels](8-secure-access-sensitivity-labels.md)
 
 9. [Secure access to Microsoft Teams, OneDrive, and SharePoint](9-secure-access-teams-sharepoint.md)
+
+10. [Secure local guest accounts](10-secure-local-guest.md)

articles/active-directory/fundamentals/secure-external-access-resources.md

@@ -318,6 +318,8 @@ items:
         href: 8-secure-access-sensitivity-labels.md
       - name: 9 Secure access to Teams, SharePoint, and OneDrive
         href: 9-secure-access-teams-sharepoint.md
+      - name: 10 Secure local guest accounts
+        href: 10-secure-local-guest.md
     - name: Secure service accounts
       items:
       - name: Introduction to Azure service accounts

articles/active-directory/fundamentals/toc.yml

@@ -7,8 +7,8 @@ manager: CelesteDG
 ms.service: active-directory
 ms.subservice: app-mgmt
 ms.workload: identity
-ms.topic: how-to
-ms.date: 06/10/2022
+ms.topic: conceptual
+ms.date: 11/02/2022
 ms.author: ergreenl
 ms.collection: M365-identity-device-management
 

articles/active-directory/manage-apps/admin-consent-workflow-overview.md

@@ -1,5 +1,5 @@
 ---
-title: Disable how a how a user signs in
+title: Disable user sign-in for application
 description: How to disable an enterprise application so that no users may sign in to it in Azure Active Directory
 services: active-directory
 author: eringreenlee
@@ -12,19 +12,19 @@ ms.date: 09/06/2022
 ms.author: ergreenl
 ms.custom: it-pro
 ms.collection: M365-identity-device-management
-#customer intent: As an admin, I want to disable the way a user signs in for an application so that no user can sign in to it in Azure Active Directory.
+#customer intent: As an admin, I want to disable user sign-in for an application so that no user can sign in to it in Azure Active Directory.
 ---
 # Disable user sign-in for an application
 
 There may be situations while configuring or managing an application where you don't want tokens to be issued for an application. Or, you may want to preemptively block an application that you do not want your employees to try to access. To accomplish this, you can disable user sign-in for the application, which will prevent all tokens from being issued for that application.
 
-In this article, you will learn how to disable how a user signs in to an application in Azure Active Directory through both the Azure portal and PowerShell. If you are looking for how to block specific users from accessing an application, use [user or group assignment](./assign-user-or-group-access-portal.md).
+In this article, you will learn how to prevent users from signing in to an application in Azure Active Directory through both the Azure portal and PowerShell. If you are looking for how to block specific users from accessing an application, use [user or group assignment](./assign-user-or-group-access-portal.md).
 
 
 
 ## Prerequisites
 
-To disable how a user signs in, you need:
+To disable user sign-in, you need:
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 - One of the following roles: Global Administrator, Cloud Application Administrator, Application Administrator, or owner of the service principal.

articles/active-directory/manage-apps/disable-user-sign-in-portal.md

@@ -8,7 +8,7 @@ ms.service: active-directory
 ms.subservice: app-mgmt
 ms.topic: how-to
 ms.workload: identity
-ms.date: 07/28/2022
+ms.date: 11/02/2022
 ms.author: jomondi
 ms.reviewer: sureshja
 ms.custom: mode-other
@@ -53,8 +53,11 @@ To recover your enterprise application with its previous configurations, first d
 1. To view the recently deleted enterprise application, run the following command:
 
    ```powershell
-   Get-AzureADMSDeletedDirectoryObject -Id 'd4142c52-179b-4d31-b5b9-08940873507b'
-   ```   
+   Get-AzureADMSDeletedDirectoryObject -Id <id>
+   ```
+
+Replace id with the object ID of the service principal that you want to restore.
+ 
 :::zone-end
 
 :::zone pivot="ms-powershell"
@@ -64,8 +67,10 @@ To recover your enterprise application with its previous configurations, first d
 1. To view the recently deleted enterprise applications, run the following command:
 
    ```powershell
-   Get-MgDirectoryDeletedItem -DirectoryObjectId 'd4142c52-179b-4d31-b5b9-08940873507b'
+   Get-MgDirectoryDeletedItem -DirectoryObjectId <id>
    ```
+Replace id with the object ID of the service principal that you want to restore.
+
 :::zone-end
 
 :::zone pivot="ms-graph"
@@ -77,7 +82,11 @@ To get the list of deleted enterprise applications in your tenant, run the follo
    ```http
    GET https://graph.microsoft.com/v1.0/directory/deletedItems/microsoft.graph.servicePrincipal
    ```
-Record the ID of the enterprise application you want to restore.
+From the list of deleted service principals generated, record the ID of the enterprise application you want to restore.
+
+Alternatively, if you want to get the specific enterprise application that was deleted, fetch the deleted service principal and filter the results by the client's application ID (appId) property using the following syntax:
+
+`https://graph.microsoft.com/v1.0/directory/deletedItems/microsoft.graph.servicePrincipal?$filter=appId eq '{appId}'`. Once you've retrieved the object ID of the deleted service principal, proceed to restore it.
 
 :::zone-end
 
@@ -89,17 +98,23 @@ Record the ID of the enterprise application you want to restore.
 
 
    ```powershell  
-   Restore-AzureADMSDeletedDirectoryObject -Id 'd4142c52-179b-4d31-b5b9-08940873507b'
+   Restore-AzureADMSDeletedDirectoryObject -Id <id>
    ```
+
+Replace id with the object ID of the service principal that you want to restore.
+
 :::zone-end
 
 :::zone pivot="ms-powershell"
 
 1. To restore the enterprise application, run the following command:
 
    ```powershell   
-   Restore-MgDirectoryObject -DirectoryObjectId 'd4142c52-179b-4d31-b5b9-08940873507b'
+   Restore-MgDirectoryObject -DirectoryObjectId <id>
    ```
+
+Replace id with the object ID of the service principal that you want to restore.
+
 :::zone-end
 
 :::zone pivot="ms-graph"
@@ -109,6 +124,9 @@ Record the ID of the enterprise application you want to restore.
    ```http
    POST https://graph.microsoft.com/v1.0/directory/deletedItems/{id}/restore
    ```
+
+Replace id with the object ID of the service principal that you want to restore.
+
 :::zone-end
 
 ## Permanently delete an enterprise application
@@ -121,7 +139,7 @@ Record the ID of the enterprise application you want to restore.
 To permanently delete a soft deleted enterprise application, run the following command:
 
 ```powershell
-Remove-AzureADMSDeletedDirectoryObject -Id 'd4142c52-179b-4d31-b5b9-08940873507b'
+Remove-AzureADMSDeletedDirectoryObject -Id <id>
 ```
 :::zone-end
 
@@ -130,7 +148,7 @@ Remove-AzureADMSDeletedDirectoryObject -Id 'd4142c52-179b-4d31-b5b9-08940873507b
 1. To permanently delete the soft deleted enterprise application, run the following command:
 
    ```powershell
-   Remove-MgDirectoryDeletedItem -DirectoryObjectId 'd4142c52-179b-4d31-b5b9-08940873507b'
+   Remove-MgDirectoryDeletedItem -DirectoryObjectId <id>
    ``` 
 
 :::zone-end