Merge pull request #242309 from MicrosoftDocs/main

6/21/2023 10AM Publishing

Author: huypub

.openpublishing.redirection.json

@@ -22203,6 +22203,16 @@
             "redirect_url": "/azure/active-directory/develop/zero-trust-for-developers",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/active-directory/develop/active-directory-v2-protocols.md",
+            "redirect_url": "/azure/active-directory/develop/v2-protocols",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/active-directory/develop/msal-net-aad-b2c-considerations.md",
+            "redirect_url": "/azure/active-directory/develop/msal-net-b2c-considerations",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/active-directory/develop/active-directory-how-applications-are-added.md",
             "redirect_url": "/azure/active-directory/develop/how-applications-are-added",

articles/active-directory/authentication/howto-authentication-passwordless-phone.md

@@ -87,14 +87,17 @@ Users can register for passwordless phone sign-in directly within the Microsoft
 6. Once signed-in, continue following the additional steps to set up phone sign-in. 
 
 ### Guided registration with My Sign-ins 
+> [!NOTE]
+> Users will only be able to register Microsoft Authenticator via combined registration if the Microsoft Authenticator authentication mode is to  Any or Push. 
+
 To register the Microsoft Authenticator app, follow these steps:
 
 1. Browse to [https://aka.ms/mysecurityinfo](https://aka.ms/mysecurityinfo).
 1. Sign in, then select **Add method** > **Authenticator app** > **Add** to add Microsoft Authenticator.
 1. Follow the instructions to install and configure the Microsoft Authenticator app on your device.
 1. Select **Done** to complete Microsoft Authenticator configuration.
 
-### Enable phone sign-in
+#### Enable phone sign-in
 
 After users registered themselves for the Microsoft Authenticator app, they need to enable phone sign-in: 
 

articles/active-directory/develop/TOC.yml

@@ -21,7 +21,7 @@
         - name: Authentication vs. authorization
           href: authentication-vs-authorization.md
         - name: OAuth 2.0 and OpenID Connect
-          href: active-directory-v2-protocols.md
+          href: v2-protocols.md
         - name: App types and authentication flows
           displayName: Auth flows
           href: authentication-flows-app-scenarios.md
@@ -762,7 +762,7 @@
                 - name: Integrate with AD FS
                   href: msal-net-adfs-support.md
                 - name: Integrate with Azure AD B2C
-                  href: msal-net-aad-b2c-considerations.md
+                  href: msal-net-b2c-considerations.md
             - name: Logging and error handling
               displayName: MSAL.NET
               items:

articles/active-directory/develop/msal-net-aad-b2c-considerations.md renamed to articles/active-directory/develop/msal-net-b2c-considerations.md

@@ -159,7 +159,7 @@ MSAL.NET supports a [token cache](/dotnet/api/microsoft.identity.client.tokencac
 
 Currently, MSAL.NET needs two claims to build a token cache key:
 
-- `tid` (the Azure AD tenant ID)
+- `tid` (the tenant ID)
 - `preferred_username`
 
 Both of these claims may be missing in Azure AD B2C scenarios because not all social identity providers (Facebook, Google, and others) return them in the tokens they return to Azure AD B2C.

articles/active-directory/develop/active-directory-v2-protocols.md renamed to articles/active-directory/develop/v2-protocols.md

@@ -219,7 +219,7 @@ Then when a Litware employee wishes to access a Contoso app, they can do so by a
 
 ### Option 8 - Configure B2B but with a common HR feed for both directories
 
-In some situations, after acquisition the organization may converge on a single HR platform, but still run existing identity management systems. In this scenario, MIM could provision users into multiple Active Directory systems, depending on with part of the organization the user is affiliated with. They could continue to use B2B so that users authenticate their existing directory, and have a unified GAL.
+In some situations, after acquisition the organization may converge on a single HR platform, but still run existing identity management systems. In this scenario, MIM could provision users into multiple Active Directory systems, depending on which part of the organization the user is affiliated with. They could continue to use B2B so that users authenticate their existing directory, and have a unified GAL.
 
 ![Configure B2B users but with a common HR system feed](media/parallel-identity-options/identity-combined-8.png)
 

articles/active-directory/fundamentals/parallel-identity-options.md

@@ -288,6 +288,10 @@ Expand the PVC by increasing the `spec.resources.requests.storage` field running
 kubectl patch pvc pvc-azuredisk --type merge --patch '{"spec": {"resources": {"requests": {"storage": "15Gi"}}}}'
 ```
 
+> [!NOTE]
+> Shrinking persistent volumes is currently not supported. Trying to patch an existing PVC with a smaller size than the current one leads to the following error message:
+> `The persistentVolumeClaim "pvc-azuredisk" is invalid: spec.resources.requests.storage: Forbidden: field can not be less than previous value.`
+
 The output of the command resembles the following example:
 
 ```output

articles/aks/azure-disk-csi.md

@@ -134,7 +134,7 @@ az aks create \
 ## Get cluster credentials 
 
 ```azurecli-interactive
-az aks get-credentials -name myAKSCluster --resource-group myResourceGroup
+az aks get-credentials --name myAKSCluster --resource-group myResourceGroup
 ```
 
 ## Enable Visualization on Grafana

articles/aks/network-observability-byo-cli.md

@@ -182,7 +182,7 @@ Use [az aks update](/cli/azure/aks#az-aks-update) to link the Azure Monitor and
 az aks update \
     --name myAKSCluster \
     --resource-group myResourceGroup \
-    --enable-azuremonitormetrics \
+    --enable-azure-monitor-metrics \
     --azure-monitor-workspace-resource-id $azuremonitorId \
     --grafana-resource-id $grafanaId
 ```
@@ -192,7 +192,7 @@ az aks update \
 ## Get cluster credentials 
 
 ```azurecli-interactive
-az aks get-credentials -name myAKSCluster --resource-group myResourceGroup
+az aks get-credentials --name myAKSCluster --resource-group myResourceGroup
 ```
 
 

articles/aks/network-observability-managed-cli.md

@@ -41,7 +41,7 @@ View the upcoming version releases on the AKS Kubernetes release calendar. To se
 > [!NOTE]
 > AKS follows 12 months of support for a generally available (GA) Kubernetes version. To read more about our support policy for Kubernetes versioning, please read our [FAQ](./supported-kubernetes-versions.md#faq).
 
-For the past release history, see [Kubernetes history](https://en.wikipedia.org/wiki/Kubernetes#History).
+For the past release history, see [Kubernetes history](https://github.com/kubernetes/kubernetes/releases).
 
 |  K8s version | Upstream release  | AKS preview  | AKS GA  | End of life |
 |--------------|-------------------|--------------|---------|-------------|