Merge pull request #208490 from MicrosoftDocs/main

Publish to Live, Friday 4AM PST, 8/19

Author: PMEds28

articles/active-directory-b2c/TOC.yml

@@ -355,7 +355,7 @@
       items:
       - name: Multi-factor authentication
         href: multi-factor-authentication.md
-        displayName: TOTP, time-based-one-time password, time-based one-time password, authenticator app, Microsoft authenticator app, mfa, 2fa
+        displayName: TOTP, multi-factor, multifactor, time-based-one-time password, time-based one-time password, authenticator app, Microsoft authenticator app, mfa, 2fa
       - name: Partner integration
         items:
         - name: Asignio

articles/active-directory/manage-apps/datawiza-azure-ad-sso-oracle-jde.md

@@ -98,7 +98,7 @@ To integrate Oracle JDE with Azure AD:
    |:-----|:-------|
    | Platform | Web |
    | App Name | Enter a unique application name.|
-   | Public Domain | For example: https:/jde-external.example.com. <br>For testing, you can use localhost DNS. If you aren't deploying DAB behind a load balancer, use the **Public Domain** port. |
+   | Public Domain | For example: `https://jde-external.example.com`. <br>For testing, you can use localhost DNS. If you aren't deploying DAB behind a load balancer, use the **Public Domain** port. |
    | Listen Port | The port that DAB listens on.|
    | Upstream Servers | The Oracle JDE implementation URL and port to be protected.|
 

articles/active-directory/saas-apps/tickitlms-learn-tutorial.md

@@ -73,7 +73,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 1. Click **Set additional URLs** and perform the following step if you wish to configure the application in **SP** initiated mode:
 
    In the **Sign-on URL** text box, type the URL:
-   `https:/learn.tickitlms.com/sso/login`
+   `https://learn.tickitlms.com/sso/login`
 
 1. Click **Save**.
 

articles/active-directory/verifiable-credentials/admin-api.md

@@ -1048,17 +1048,17 @@ Don't supply a request body for this method.
 
 example message:
 
-```
+```json
 {
-    value:
+    "value":
     [
         {
             "id": "ZjViZjJmYzYtNzEzNS00ZDk0LWE2ZmUtYzI2ZTQ1NDNiYzVhPHNjcmlwdD5hbGVydCgneWF5IScpOzwvc2NyaXB0Pg",
             "name": "test1",
             "authorityId": "ffea7eb3-0000-1111-2222-000000000000",
             "status": "Enabled",
             "issueNotificationEnabled": false,
-            "manifestUrl" : "https:/...",
+            "manifestUrl" : "https://...",
             "rules": "<rules JSON>",
             "displays": [{<display JSON}]
         },
@@ -1068,7 +1068,7 @@ example message:
             "authorityId": "cc55ba22-0000-1111-2222-000000000000",
             "status": "Enabled",
             "issueNotificationEnabled": false,
-            "manifestUrl" : "https:/...",
+            "manifestUrl" : "https://...",
             "rules": "<rules JSON>",
             "displays": [{<display JSON}]
         }

articles/aks/certificate-rotation.md

@@ -11,7 +11,7 @@ ms.date: 5/10/2022
 Azure Kubernetes Service (AKS) uses certificates for authentication with many of its components. If you have a RBAC-enabled cluster built after March 2022 it is enabled with certificate auto-rotation. Periodically, you may need to rotate those certificates for security or policy reasons. For example, you may have a policy to rotate all your certificates every 90 days.
 
 > [!NOTE]
-> Certificate auto-rotation will not be enabled by default for non-RBAC enabled AKS clusters.
+> Certificate auto-rotation will *only* be enabled by default for RBAC enabled AKS clusters. 
 
 This article shows you how certificate rotation works in your AKS cluster.
 
@@ -55,10 +55,11 @@ az vmss run-command invoke -g MC_rg_myAKSCluster_region -n vmss-name --instance-
 
 ## Certificate Auto Rotation
 
-For AKS to automatically rotate non-CA certificates, the cluster must have [TLS Bootstrapping](https://kubernetes.io/docs/reference/access-authn-authz/kubelet-tls-bootstrapping/) which has been enabled by default in all Azure regions.
+For AKS to automatically rotate non-CA certificates, the cluster must have [TLS Bootstrapping](https://kubernetes.io/docs/reference/access-authn-authz/kubelet-tls-bootstrapping/) which has been enabled by default in all Azure regions. 
 
 > [!Note]
 > If you have an existing cluster you have to upgrade that cluster to enable Certificate Auto-Rotation.
+> Do not disable bootstrap to keep your auto-rotation enabled. 
 
 For any AKS clusters created or upgraded after March 2022 Azure Kubernetes Service will automatically rotate non-CA certificates on both the control plane and agent nodes within 80% of the client certificate valid time, before they expire with no downtime for the cluster.
 
@@ -82,7 +83,7 @@ az aks upgrade -g $RESOURCE_GROUP_NAME -n $CLUSTER_NAME
 
 ### Limitation
 
-Auto certificate rotation won't be enabled on a non-RBAC cluster.
+Certificate auto-rotation will only be enabled by default for RBAC enabled AKS clusters.
 
 ## Manually rotate your cluster certificates
 

articles/aks/integrations.md

@@ -22,6 +22,12 @@ The following rules are used by AKS for applying updates to installed add-ons:
 - Any breaking or behavior changes to the add-on will be announced well before, usually 60 days, a later minor version of Kubernetes is released on AKS.
 - Add-ons can be patched weekly with every new release of AKS which will be announced in the release notes. AKS releases can be controlled using [maintenance windows][maintenance-windows] and followed using [release tracker][release-tracker].
 
+### Exceptions 
+
+The following exceptions apply to bringing in major/minor or breaking changes to the add-ons:
+ - In the event that the Kubernetes version is in preview
+ - In the event that the addon or feature is in preview
+
 The below table shows the available add-ons.
 
 | Name | Description | More details |

articles/aks/scale-cluster.md

@@ -8,7 +8,7 @@ ms.date: 06/29/2022
 
 # Scale the node count in an Azure Kubernetes Service (AKS) cluster
 
-If the resource needs of your applications change, you can manually scale an AKS cluster to run a different number of nodes. When you scale down, nodes are carefully [cordoned and drained][kubernetes-drain] to minimize disruption to running applications. When you scale up, AKS waits until nodes are marked **Ready** by the Kubernetes cluster before pods are scheduled on them.
+If the resource needs of your applications change, your cluster performance may be impacted due to low capacity on CPU, memory, PID space, or disk sizes. To address these changes, you can manually scale your AKS cluster to run a different number of nodes. When you scale down, nodes are carefully [cordoned and drained][kubernetes-drain] to minimize disruption to running applications. When you scale up, AKS waits until nodes are marked **Ready** by the Kubernetes cluster before pods are scheduled on them.
 
 ## Scale the cluster nodes
 
@@ -165,4 +165,4 @@ In this article, you manually scaled an AKS cluster to increase or decrease the
 [set-azakscluster]: /powershell/module/az.aks/set-azakscluster
 [cluster-autoscaler]: cluster-autoscaler.md
 [az-aks-nodepool-scale]: /cli/azure/aks/nodepool#az_aks_nodepool_scale
-[update-azaksnodepool]: /powershell/module/az.aks/update-azaksnodepool
+[update-azaksnodepool]: /powershell/module/az.aks/update-azaksnodepool

articles/app-service/tutorial-dotnetcore-sqldb-app.md

@@ -260,7 +260,7 @@ Azure App Service provides a web-based diagnostics console named Kudu. Kudu lets
 
 To use Kudu, go to one of the following URLs. You'll need to sign into the Kudu site with your Azure credentials.
 
-* For apps deployed in Free, Shared, Basic, Standard, and Premium App Service plans - `https:/<app-name>.scm.azurewebsites.net`
+* For apps deployed in Free, Shared, Basic, Standard, and Premium App Service plans - `https://<app-name>.scm.azurewebsites.net`
 * For apps deployed in Isolated service plans - `https://<app-name>.scm.<ase-name>.p.azurewebsites.net`
 From the main page in Kudu, you can find information about the application-hosting environment, app settings, deployments, and browse the files in the wwwroot directory.
 

articles/azure-app-configuration/cli-samples.md

@@ -1,8 +1,8 @@
 ---
 title: Azure CLI samples - Azure App Configuration
 description: Information about sample scripts provided for Azure App Configuration
-author: AlexandraKemperMS
-ms.author: alkemper
+author: maud-lv
+ms.author: malev
 ms.service: azure-app-configuration
 ms.topic: sample
 ms.date: 02/19/2020 

articles/azure-app-configuration/concept-customer-managed-keys.md

@@ -1,8 +1,8 @@
 ---
 title: Use customer-managed keys to encrypt your configuration data 
 description: Encrypt your configuration data using customer-managed keys
-author: AlexandraKemperMS
-ms.author: alkemper
+author: maud-lv
+ms.author: malev
 ms.date: 07/28/2020
 ms.topic: conceptual
 ms.service: azure-app-configuration