Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into mar15-metarefresh-twins

Author: kgremban

articles/active-directory-b2c/custom-policies-series-call-rest-api.md

@@ -10,7 +10,7 @@ ms.service: active-directory
 ms.workload: identity
 ms.topic: how-to
 ms.custom: b2c-docs-improvements
-ms.date: 01/30/2023
+ms.date: 03/16/2023
 ms.author: kengaderdus
 ms.reviewer: yoelh
 ms.subservice: B2C
@@ -302,6 +302,12 @@ Then, update the *Metadata*, *InputClaimsTransformations*, and *InputClaims* of
     </InputClaims>
 ```
 
+## Receive data from REST API
+
+If your REST API returns data, which you want to include as claims in your policy, you can receive it by specifying claims in the `OutputClaims` element of the RESTful technical profile. If the name of the claim defined in your policy is different from the name defined in the REST API, you need to map these names by using the `PartnerClaimType` attribute. 
+
+Use the steps in [Receiving data](api-connectors-overview.md?pivots=b2c-custom-policy#receiving-data) to learn how to format the data the custom policy expects, how to handle nulls values, and how to parse REST the API's nested JSON body.
+
 ## Next steps
 
 Next, learn:

articles/active-directory-b2c/custom-policies-series-hello-world.md

@@ -10,7 +10,7 @@ ms.service: active-directory
 ms.workload: identity
 ms.topic: how-to
 ms.custom: b2c-docs-improvements
-ms.date: 01/30/2023
+ms.date: 03/16/2023
 ms.author: kengaderdus
 ms.reviewer: yoelh
 ms.subservice: B2C
@@ -280,7 +280,7 @@ After the policy finishes execution, you're redirected to `https://jwt.ms`, and
     }.[Signature]
 ``` 
 
-Notice the `message` and `sub` claims, which we set as output claims](relyingparty.md#outputclaims) in the `RelyingParty` section. 
+Notice the `message` and `sub` claims, which we set as [output claims](relyingparty.md#outputclaims) in the `RelyingParty` section. 
 
 ## Next steps
 

articles/active-directory-domain-services/troubleshoot-alerts.md

@@ -10,7 +10,7 @@ ms.service: active-directory
 ms.subservice: domain-services
 ms.workload: identity
 ms.topic: troubleshooting
-ms.date: 03/02/2023
+ms.date: 03/15/2023
 ms.author: justinha
 
 ---
@@ -314,6 +314,19 @@ When the managed domain is enabled again, the managed domain's health automatica
 
 [Check the Azure AD DS health](check-health.md) for alerts that indicate problems in the configuration of the managed domain. If you're able to resolve alerts that indicate a configuration issue, wait two hours and check back to see if the synchronization has completed. When ready, [open an Azure support request][azure-support] to re-enable the managed domain.
 
+## AADDS600: Unresolved health alerts for 30 days
+
+### Alert Message
+
+*Microsoft can’t manage the domain controllers for this managed domain due to unresolved health alerts \[IDs\]. This is blocking critical security updates as well as a planned migration to Windows Server 2019 for these domain controllers. Follow steps in the alert to resolve the issue. Failure to resolve this issue within 30 days will result in suspension of the managed domain.*
+
+### Resolution
+
+> [!WARNING]
+> If a managed domain is suspended for an extended period of time, there's a danger of it being deleted. Resolve the reason for suspension as quickly as possible. For more information, see [Understand the suspended states for Azure AD DS](suspension.md).
+
+[Check the Azure AD DS health](check-health.md) for alerts that indicate problems in the configuration of the managed domain. If you're able to resolve alerts that indicate a configuration issue, wait six hours and check back to see if the alert is removed. [Open an Azure support request][azure-support] if you need assistance.
+
 ## Next steps
 
 If you still have issues, [open an Azure support request][azure-support] for additional troubleshooting assistance.

articles/azure-app-configuration/quickstart-feature-flag-spring-boot.md

@@ -74,7 +74,7 @@ To create a new Spring Boot project:
 
 > [!NOTE]
 > * If you need to support an older version of Spring Boot see our [old appconfiguration library](https://github.com/Azure/azure-sdk-for-java/blob/spring-cloud-starter-azure-appconfiguration-config_1.2.9/sdk/appconfiguration/spring-cloud-starter-azure-appconfiguration-config/README.md) and our [old feature flag library](https://github.com/Azure/azure-sdk-for-java/blob/spring-cloud-starter-azure-appconfiguration-config_1.2.9/sdk/appconfiguration/spring-cloud-azure-feature-management/README.md).
-> * There is a non-web Feature Management Library that doesn't have a dependency on spring-web. Refer to GitHub's [documentation](https://github.com/Azure/azure-sdk-for-java/tree/master/sdk/appconfiguration/azure-spring-cloud-feature-management) for differences.
+> * There is a non-web Feature Management Library that doesn't have a dependency on spring-web. Refer to GitHub's [documentation](https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/spring/spring-cloud-azure-feature-management) for differences.
 
 ## Connect to an App Configuration store
 

articles/azure-arc/data/create-data-controller-indirect-cli.md

@@ -1,6 +1,6 @@
 ---
 title: Create data controller using CLI
-description: Create an Azure Arc data controller, on a typical multi-node Kubernetes cluster which you already have created, using the CLI.
+description: Create an Azure Arc data controller, on a typical multi-node Kubernetes cluster that you already have created, using the CLI.
 services: azure-arc
 ms.service: azure-arc
 ms.subservice: azure-arc-data
@@ -20,12 +20,11 @@ Review the topic [Plan an Azure Arc-enabled data services deployment](plan-azure
 
 ### Install tools
 
-To create the data controller using the CLI, you will need to install the `arcdata` extension for Azure (az) CLI. 
+Before you begin, install the `arcdata` extension for Azure (az) CLI. 
 
 [Install the [!INCLUDE [azure-data-cli-azdata](../../../includes/azure-data-cli-azdata.md)]](install-client-tools.md)
 
-Regardless of which target platform you choose, you will need to set the following environment variables prior to the creation for the data controller. These environment variables will become the credentials used for accessing the metrics and logs dashboards after data controller creation.
-
+Regardless of which target platform you choose, you need to set the following environment variables prior to the creation for the data controller. These environment variables become the credentials used for accessing the metrics and logs dashboards after data controller creation.
 
 ### Set environment variables
 
@@ -58,7 +57,7 @@ $ENV:AZDATA_METRICSUI_PASSWORD="<password for Grafana dashboard>"
 
 ### Connect to Kubernetes cluster
 
-You will need to connect and authenticate to a Kubernetes cluster and have an existing Kubernetes context selected prior to beginning the creation of the Azure Arc data controller. How you connect to a Kubernetes cluster or service varies. See the documentation for the Kubernetes distribution or service that you are using on how to connect to the Kubernetes API server.
+Connect and authenticate to a Kubernetes cluster and have an existing Kubernetes context selected prior to beginning the creation of the Azure Arc data controller. How you connect to a Kubernetes cluster or service varies. See the documentation for the Kubernetes distribution or service that you are using on how to connect to the Kubernetes API server.
 
 You can check to see that you have a current Kubernetes connection and confirm your current context with the following commands.
 
@@ -86,7 +85,7 @@ The following sections provide instructions for specific types of Kubernetes pla
 
 ## Create on Azure Kubernetes Service (AKS)
 
-By default, the AKS deployment profile uses the `managed-premium` storage class. The `managed-premium` storage class will only work if you have VMs that were deployed using VM images that have premium disks.
+By default, the AKS deployment profile uses the `managed-premium` storage class. The `managed-premium` storage class only works if you have VMs that were deployed using VM images that have premium disks.
 
 If you are going to use `managed-premium` as your storage class, then you can run the following command to create the data controller. Substitute the placeholders in the command with your resource group name, subscription ID, and Azure location.
 
@@ -162,7 +161,7 @@ Once you have run the command, continue on to [Monitoring the creation status](#
 
 ### Determine storage class
 
-You will also need to determine which storage class to use by running the following command.
+To determine which storage class to use, run the following command.
 
 ```console
 kubectl get storageclass
@@ -204,10 +203,10 @@ az arcdata dc config replace --path ./custom/control.json --json-values "$.spec.
 Now you are ready to create the data controller using the following command.
 
 > [!NOTE]
->   The `--path` parameter should point to the _directory_ containing the control.json file not to the control.json file itself.
+>  The `--path` parameter should point to the _directory_ containing the control.json file not to the control.json file itself.
 
 > [!NOTE]
->   When deploying to OpenShift Container Platform, you will need to specify the `--infrastructure` parameter value.  Options are: `aws`, `azure`, `alibaba`, `gcp`, `onpremises`.
+> When deploying to OpenShift Container Platform, specify the `--infrastructure` parameter value.  Options are: `aws`, `azure`, `alibaba`, `gcp`, `onpremises`.
 
 ```azurecli
 az arcdata dc create --path ./custom  --k8s-namespace <namespace> --use-k8s --name arc --subscription <subscription id> --resource-group <resource group name> --location <location> --connectivity-mode indirect --infrastructure <infrastructure>
@@ -222,7 +221,7 @@ Once you have run the command, continue on to [Monitoring the creation status](#
 
 By default, the kubeadm deployment profile uses a storage class called `local-storage` and service type `NodePort`. If this is acceptable you can skip the instructions below that set the desired storage class and service type and immediately run the `az arcdata dc create` command below.
 
-If you want to customize your deployment profile to specify a specific storage class and/or service type, start by creating a new custom deployment profile file based on the kubeadm deployment profile by running the following command. This command will create a directory `custom` in your current working directory and a custom deployment profile file `control.json` in that directory.
+If you want to customize your deployment profile to specify a specific storage class and/or service type, start by creating a new custom deployment profile file based on the kubeadm deployment profile by running the following command. This command creates a directory `custom` in your current working directory and a custom deployment profile file `control.json` in that directory.
 
 ```azurecli
 az arcdata dc config init --source azure-arc-kubeadm --path ./custom 
@@ -248,13 +247,13 @@ az arcdata dc config replace --path ./custom/control.json --json-values "spec.st
 By default, the kubeadm deployment profile uses `NodePort` as the service type. If you are using a Kubernetes cluster that is integrated with a load balancer, you can change the configuration using the following command.
 
 ```azurecli
-az arcdata dc config replace --path ./custom/control.json --json-values "$.spec.services[*].serviceType=LoadBalancer" --k8s-namespace <namespace> --use-k8s
+az arcdata dc config replace --path ./custom/control.json --json-values "$.spec.services[*].serviceType=LoadBalancer"
 ```
 
 Now you are ready to create the data controller using the following command.
 
 > [!NOTE]
->   When deploying to OpenShift Container Platform, you will need to specify the `--infrastructure` parameter value.  Options are: `aws`, `azure`, `alibaba`, `gcp`, `onpremises`.
+> When deploying to OpenShift Container Platform, specify the `--infrastructure` parameter value.  Options are: `aws`, `azure`, `alibaba`, `gcp`, `onpremises`.
 
 ```azurecli
 az arcdata dc create --path ./custom  --k8s-namespace <namespace> --use-k8s --name arc --subscription <subscription id> --resource-group <resource group name> --location <location> --connectivity-mode indirect --infrastructure <infrastructure>
@@ -297,7 +296,7 @@ Once you have run the command, continue on to [Monitoring the creation status](#
 
 ## Monitor the creation status
 
-Creating the controller will take a few minutes to complete. You can monitor the progress in another terminal window with the following commands:
+It takes a few minutes to create the controller completely. You can monitor the progress in another terminal window with the following commands:
 
 > [!NOTE]
 > The example commands below assume that you created a data controller named `arc-dc` and Kubernetes namespace named `arc`. If you used different values update the script accordingly.