Merge branch 'main' into release-arc-data

Author: v-alje

.openpublishing.redirection.json

@@ -5963,11 +5963,6 @@
             "redirect_url": "/azure/reliability/cross-region-replication-azure",
             "redirect_document_id": true
         },
-        {
-            "source_path_from_root": "/articles/partner-solutions/index.md",
-            "redirect_url": "/azure/partner-solutions/overview",
-            "redirect_document_id": false
-        },
         {
             "source_path_from_root": "/articles/fxt-edge-filer/fxt-add-nodes.md",
             "redirect_url": "/azure/fxt-edge-filer/add-nodes",
@@ -6358,6 +6353,11 @@
             "redirect_url": "/azure/azure-cache-for-redis/scripts/create-manage-cache",
             "redirect_document_id": false
         },
+        { 
+            "source_path_from_root": "/articles/storage/blobs/anonymous-read-access-client.md",
+            "redirect_url": "/azure/storage/blobs/anonymous-read-access-prevent",
+            "redirect_document_id": false
+        },
         { 
             "source_path_from_root": "/articles/storage/common/storage-auth-abac-attributes.md",
             "redirect_url": "/azure/storage/blobs/storage-auth-abac-attributes",

articles/active-directory-b2c/microsoft-graph-operations.md

@@ -39,7 +39,7 @@ To use MS Graph API, and interact with resources in your Azure AD B2C tenant, yo
 - [Update a user](/graph/api/user-update)
 - [Delete a user](/graph/api/user-delete)
 
-## User phone number management (beta)
+## User phone number management
 
 A phone number that can be used by a user to sign-in using [SMS or voice calls](sign-in-options.md#phone-sign-in), or [multifactor authentication](multi-factor-authentication.md). For more information, see [Azure AD authentication methods API](/graph/api/resources/phoneauthenticationmethod).
 
@@ -54,9 +54,9 @@ Note, the [list](/graph/api/authentication-list-phonemethods) operation returns
 ![Enable phone sign-in](./media/microsoft-graph-operations/enable-phone-sign-in.png)
 
 > [!NOTE]
-> In the current beta version, this API works only if the phone number is stored with a space between the country code and the phone number. The Azure AD B2C service doesn't currently add this space by default.
+> A correctly represented phone number is stored with a space between the country code and the phone number. The Azure AD B2C service doesn't currently add this space by default.
 
-## Self-service password reset email address (beta)
+## Self-service password reset email address
 
 An email address that can be used by a [username sign-in account](sign-in-options.md#username-sign-in) to reset the password. For more information, see [Azure AD authentication methods API](/graph/api/resources/emailauthenticationmethod).
 
@@ -66,7 +66,7 @@ An email address that can be used by a [username sign-in account](sign-in-option
 - [Update](/graph/api/emailauthenticationmethod-update)
 - [Delete](/graph/api/emailauthenticationmethod-delete)
 
-## Software OATH token authentication method (beta)
+## Software OATH token authentication method
 
  A software OATH token is a software-based number generator that uses the OATH time-based one-time password (TOTP) standard for multifactor authentication via an authenticator app. Use the Microsoft Graph API to manage a software OATH token registered to a user:
 
@@ -78,13 +78,14 @@ An email address that can be used by a [username sign-in account](sign-in-option
 
 Manage the [identity providers](add-identity-provider.md) available to your user flows in your Azure AD B2C tenant.
 
-- [List identity providers registered in the Azure AD B2C tenant](/graph/api/identityprovider-list)
-- [Create an identity provider](/graph/api/identityprovider-post-identityproviders)
-- [Get an identity provider](/graph/api/identityprovider-get)
-- [Update identity provider](/graph/api/identityprovider-update)
-- [Delete an identity provider](/graph/api/identityprovider-delete)
+- [List identity providers available in the Azure AD B2C tenant](/graph/api/identityproviderbase-availableprovidertypes)
+- [List identity providers configured in the Azure AD B2C tenant](/graph/api/iidentitycontainer-list-identityproviders)
+- [Create an identity provider](/graph/api/identitycontainer-post-identityproviders)
+- [Get an identity provider](/graph/api/identityproviderbase-get)
+- [Update identity provider](/graph/api/identityproviderbase-update)
+- [Delete an identity provider](/graph/api/identityproviderbase-delete)
 
-## User flow
+## User flow (beta)
 
 Configure pre-built policies for sign-up, sign-in, combined sign-up and sign-in, password reset, and profile update.
 
@@ -100,7 +101,7 @@ Choose a mechanism for letting users register via local accounts. Local accounts
 - [Get](/graph/api/b2cauthenticationmethodspolicy-get)
 - [Update](/graph/api/b2cauthenticationmethodspolicy-update)
 
-## Custom policies
+## Custom policies (beta)
 
 The following operations allow you to manage your Azure AD B2C Trust Framework policies, known as [custom policies](custom-policy-overview.md).
 
@@ -110,7 +111,7 @@ The following operations allow you to manage your Azure AD B2C Trust Framework p
 - [Update or create trust framework policy.](/graph/api/trustframework-put-trustframeworkpolicy)
 - [Delete an existing trust framework policy](/graph/api/trustframeworkpolicy-delete)
 
-## Policy keys
+## Policy keys (beta)
 
 The Identity Experience Framework stores the secrets referenced in a custom policy to establish trust between components. These secrets can be symmetric or asymmetric keys/values. In the Azure portal, these entities are shown as **Policy keys**.
 
@@ -169,15 +170,16 @@ For more information about accessing Azure AD B2C audit logs, see [Accessing Azu
 
 ## Conditional Access
 
-- [List all of the Conditional Access policies](/graph/api/conditionalaccessroot-list-policies?tabs=http)
+- [List the built-in templates for Conditional Access policy scenarios](/graph/api/conditionalaccessroot-list-templates)
+- [List all of the Conditional Access policies](/graph/api/conditionalaccessroot-list-policies)
 - [Read properties and relationships of a Conditional Access policy](/graph/api/conditionalaccesspolicy-get)
 - [Create a new Conditional Access policy](/graph/api/resources/application)
 - [Update a Conditional Access policy](/graph/api/conditionalaccesspolicy-update)
 - [Delete a Conditional Access policy](/graph/api/conditionalaccesspolicy-delete)
 
 ## Retrieve or restore deleted users and applications
 
-Deleted items can only be restored if they were deleted within the last 30 days.
+Deleted users and apps can only be restored if they were deleted within the last 30 days.
 
 - [List deleted items](/graph/api/directory-deleteditems-list)
 - [Get a deleted item](/graph/api/directory-deleteditems-get)

articles/active-directory/app-proxy/application-proxy-configure-native-client-application.md

@@ -112,6 +112,6 @@ After you edit the MSAL code with these parameters, your users can authenticate
 
 ## Next steps
 
-For more information about the native application flow, see [Native apps in Azure Active Directory](../azuread-dev/native-app.md).
+For more information about the native application flow, see [mobile](../develop/authentication-flows-app-scenarios.md#mobile-app-that-calls-a-web-api-on-behalf-of-an-interactive-user) and [desktop](../develop/authentication-flows-app-scenarios.md#desktop-app-that-calls-a-web-api-on-behalf-of-a-signed-in-user) apps in Azure Active Directory.
 
 Learn about setting up [Single sign-on to applications in Azure Active Directory](../manage-apps/sso-options.md#choosing-a-single-sign-on-method).

articles/active-directory/authentication/concept-certificate-based-authentication-smartcard.md

@@ -6,7 +6,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: authentication
 ms.topic: how-to
-ms.date: 10/05/2022
+ms.date: 11/10/2022
 
 ms.author: justinha
 author: vimrang
@@ -77,7 +77,7 @@ The Windows smart card sign-in works with the latest preview build of Windows 11
 
 ## Restrictions and caveats  
 
-- Azure AD CBA is supported on Windows Hybrid or Azure AD Joined.  
+- Azure AD CBA is supported on Windows devices that are hybrid or Azure AD joined.  
 - Users must be in a managed domain or using Staged Rollout and can't use a federated authentication model.
 
 ## Next steps

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

@@ -147,7 +147,7 @@ Users with a Temporary Access Pass can navigate the setup process on Windows 10
 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. 
+- If the [Web sign-in](/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. 

articles/active-directory/authentication/howto-authentication-use-email-signin.md

@@ -153,7 +153,7 @@ With the policy applied, it can take up to 1 hour to propagate and for users to
 ### PowerShell
 
 > [!NOTE]
-> This configuration option uses HRD policy. For more information, see [homeRealmDiscoveryPolicy resource type](/graph/api/resources/homeRealmDiscoveryPolicy?view=graph-rest-1.0).
+> This configuration option uses HRD policy. For more information, see [homeRealmDiscoveryPolicy resource type](/graph/api/resources/homeRealmDiscoveryPolicy?view=graph-rest-1.0&preserve-view=true).
 
 Once users with the *ProxyAddresses* attribute applied are synchronized to Azure AD using Azure AD Connect, you need to enable the feature for users to sign-in with email as an alternate login ID for your tenant. This feature tells the Azure AD login servers to not only check the sign-in identifier against UPN values, but also against *ProxyAddresses* values for the email address.