Merge pull request #195117 from MicrosoftDocs/main

4/14 AM Publish

Author: huypub

articles/active-directory-domain-services/TOC.yml

@@ -91,6 +91,8 @@
           href: migrate-from-classic-vnet.md
         - name: Change SKU
           href: change-sku.md
+        - name: Retrieve data
+          href: how-to-data-retrieval.md
     - name: Secure Azure AD DS
       items:
         - name: Secure your managed domain

articles/active-directory-domain-services/how-to-data-retrieval.md

@@ -0,0 +1,99 @@
+---
+title: Instructions for data retrieval from Azure Active Directory Domain Services | Microsoft Docs
+description: Learn how to retrieve data from Azure Active Directory Domain Services (Azure AD DS).
+services: active-directory-ds
+author: justinha
+manager: karenhoran
+
+ms.service: active-directory
+ms.subservice: domain-services
+ms.workload: identity
+ms.topic: conceptual
+ms.date: 04/14/2022
+ms.author: justinha
+ms.reviewer: manthanm
+---
+
+# Azure AD DS instructions for data retrieval
+
+This document describes how to retrieve data from Azure Active Directory Domain Services (Azure AD DS).
+
+[!INCLUDE [active-directory-app-provisioning.md](../../includes/gdpr-intro-sentence.md)]
+
+## Use Azure Active Directory to create, read, update, and delete user objects
+
+You can create a user in the Azure AD portal or by using Graph PowerShell or Graph API. You can also read, update, and delete users. The next sections show how to do these operations in the Azure AD portal. 
+
+### Create, read, or update a user
+
+You can create a new user using the Azure Active Directory portal.
+To add a new user, follow these steps:
+
+1. Sign in to the [Azure portal](https://portal.azure.com/) in the User Administrator role for the organization.
+
+1. Search for and select *Azure Active Directory* from any page.
+
+1. Select **Users**, and then select **New user**.
+
+    ![Add a user through Users - All users in Azure AD](./media/tutorial-create-management-vm/add-user-in-users-all-users.png)
+
+1. On the **User** page, enter information for this user:
+
+   - **Name**. Required. The first and last name of the new user. For example, *Mary Parker*.
+
+   - **User name**. Required. The user name of the new user. For example, `[email protected]`.
+
+   - **Groups**. Optionally, you can add the user to one or more existing groups. 
+
+   - **Directory role**: If you require Azure AD administrative permissions for the user, you can add them to an Azure AD role. 
+
+   - **Job info**: You can add more information about the user here.
+
+1. Copy the autogenerated password provided in the **Password** box. You'll need to give this password to the user to sign in for the first time.
+
+1. Select **Create**.
+
+The user is created and added to your Azure AD organization.
+
+To read or update a user, search for and select the user such as, _Mary Parker_. Change any property and click **Save**. 
+
+### Delete a user
+
+To delete a user, follow these steps:
+
+1. Search for and select the user you want to delete from your Azure AD tenant. For example, _Mary Parker_.
+
+1. Select **Delete user**.
+
+   ![Users - All users page with Delete user highlighted](./media/tutorial-create-management-vm/delete-user-all-users-blade.png)
+
+
+The user is deleted and no longer appears on the **Users - All users** page. The user can be seen on the **Deleted users** page for the next 30 days and can be restored during that time. 
+
+When a user is deleted, any licenses consumed by the user are made available for other users.
+
+## Use RSAT tools to connect to an Azure AD DS managed domain and view users
+
+Sign in to an administrative workstation with a user account that's a member of the *AAD DC Administrators* group. The following steps require installation of [Remote Server Administration Tools (RSAT)](tutorial-create-management-vm.md#install-active-directory-administrative-tools).
+
+1. From the **Start** menu, select **Windows Administrative Tools**. The Active Directory Administration Tools are listed.
+
+    ![List of Administrative Tools installed on the server](./media/tutorial-create-management-vm/list-admin-tools.png)
+
+1. Select **Active Directory Administrative Center**.
+1. To explore the managed domain, choose the domain name in the left pane, such as *aaddscontoso*. Two containers named *AADDC Computers* and *AADDC Users* are at the top of the list.
+
+    ![List the available containers part of the managed domain](./media/tutorial-create-management-vm/active-directory-administrative-center.png)
+
+1. To see the users and groups that belong to the managed domain, select the **AADDC Users** container. The user accounts and groups from your Azure AD tenant are listed in this container.
+
+    In the following example output, a user account named *Contoso Admin* and a group for *AAD DC Administrators* are shown in this container.
+
+    ![View the list of Azure AD DS domain users in the Active Directory Administrative Center](./media/tutorial-create-management-vm/list-azure-ad-users.png)
+
+1. To see the computers that are joined to the managed domain, select the **AADDC Computers** container. An entry for the current virtual machine, such as *myVM*, is listed. Computer accounts for all devices that are joined to the managed domain are stored in this *AADDC Computers* container.
+
+You can also use the *Active Directory Module for Windows PowerShell*, installed as part of the administrative tools, to manage common actions in your managed domain.
+
+## Next steps
+* [Azure AD DS Overview](overview.md)

articles/active-directory-domain-services/media/tutorial-create-management-vm/add-user-in-users-all-users.png

@@ -3,7 +3,7 @@ title: Using API Management service to generate HTTP requests
 description: Learn to use request and response policies in API Management to call external services from your API
 services: api-management
 documentationcenter: ''
-author: dlepow
+author: adrianhall
 manager: erikre
 editor: ''
 
@@ -12,8 +12,8 @@ ms.service: api-management
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: na
-ms.date: 12/15/2016
-ms.author: danlep
+ms.date: 04/14/2022
+ms.author: adhal
 
 ---
 # Using external services from the Azure API Management service
@@ -29,26 +29,26 @@ The following example demonstrates how to send a message to a Slack chat room if
 
 ```xml
 <choose>
-    <when condition="@(context.Response.StatusCode >= 500)">
-      <send-one-way-request mode="new">
-        <set-url>https://hooks.slack.com/services/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</set-url>
-        <set-method>POST</set-method>
-        <set-body>@{
-                return new JObject(
-                        new JProperty("username","APIM Alert"),
-                        new JProperty("icon_emoji", ":ghost:"),
-                        new JProperty("text", String.Format("{0} {1}\nHost: {2}\n{3} {4}\n User: {5}",
-                                                context.Request.Method,
-                                                context.Request.Url.Path + context.Request.Url.QueryString,
-                                                context.Request.Url.Host,
-                                                context.Response.StatusCode,
-                                                context.Response.StatusReason,
-                                                context.User.Email
-                                                ))
-                        ).ToString();
-            }</set-body>
-      </send-one-way-request>
-    </when>
+  <when condition="@(context.Response.StatusCode >= 500)">
+    <send-one-way-request mode="new">
+      <set-url>https://hooks.slack.com/services/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</set-url>
+      <set-method>POST</set-method>
+      <set-body>@{
+        return new JObject(
+          new JProperty("username","APIM Alert"),
+          new JProperty("icon_emoji", ":ghost:"),
+          new JProperty("text", String.Format("{0} {1}\nHost: {2}\n{3} {4}\n User: {5}",
+            context.Request.Method,
+            context.Request.Url.Path + context.Request.Url.QueryString,
+            context.Request.Url.Host,
+            context.Response.StatusCode,
+            context.Response.StatusReason,
+            context.User.Email
+          ))
+        ).ToString();
+      }</set-body>
+    </send-one-way-request>
+  </when>
 </choose>
 ```
 
@@ -144,17 +144,17 @@ At the end, you get the following policy:
   </send-request>
 
   <choose>
-          <!-- Check active property in response -->
-          <when condition="@((bool)((IResponse)context.Variables["tokenstate"]).Body.As<JObject>()["active"] == false)">
-              <!-- Return 401 Unauthorized with http-problem payload -->
-              <return-response response-variable-name="existing response variable">
-                  <set-status code="401" reason="Unauthorized" />
-                  <set-header name="WWW-Authenticate" exists-action="override">
-                      <value>Bearer error="invalid_token"</value>
-                  </set-header>
-              </return-response>
-          </when>
-      </choose>
+    <!-- Check active property in response -->
+    <when condition="@((bool)((IResponse)context.Variables["tokenstate"]).Body.As<JObject>()["active"] == false)">
+      <!-- Return 401 Unauthorized with http-problem payload -->
+      <return-response response-variable-name="existing response variable">
+        <set-status code="401" reason="Unauthorized" />
+        <set-header name="WWW-Authenticate" exists-action="override">
+          <value>Bearer error="invalid_token"</value>
+        </set-header>
+      </return-response>
+    </when>
+  </choose>
   <base />
 </inbound>
 ```
@@ -198,19 +198,20 @@ Once you have this information, you can make requests to all the backend systems
 </send-request>
 
 <send-request mode="new" response-variable-name="throughputdata" timeout="20" ignore-error="true">
-<set-url>@($"https://production.acme.com/throughput?from={(string)context.Variables["fromDate"]}&to={(string)context.Variables["fromDate"]}")</set-url>
+  <set-url>@($"https://production.acme.com/throughput?from={(string)context.Variables["fromDate"]}&to={(string)context.Variables["fromDate"]}")</set-url>
   <set-method>GET</set-method>
 </send-request>
 
 <send-request mode="new" response-variable-name="accidentdata" timeout="20" ignore-error="true">
-<set-url>@($"https://production.acme.com/accidentdata?from={(string)context.Variables["fromDate"]}&to={(string)context.Variables["fromDate"]}")</set-url>
+  <set-url>@($"https://production.acme.com/accidentdata?from={(string)context.Variables["fromDate"]}&to={(string)context.Variables["fromDate"]}")</set-url>
   <set-method>GET</set-method>
 </send-request>
 ```
 
-These requests execute in sequence, which is not ideal. 
+API Management will send these requests sequentially.
 
 ### Responding
+
 To construct the composite response, you can use the [return-response](./api-management-advanced-policies.md#ReturnResponse) policy. The `set-body` element can use an expression to construct a new `JObject` with all the component representations embedded as properties.
 
 ```xml
@@ -233,10 +234,9 @@ The complete policy looks as follows:
 
 ```xml
 <policies>
-    <inbound>
-
-  <set-variable name="fromDate" value="@(context.Request.Url.Query["fromDate"].Last())">
-  <set-variable name="toDate" value="@(context.Request.Url.Query["toDate"].Last())">
+  <inbound>
+    <set-variable name="fromDate" value="@(context.Request.Url.Query["fromDate"].Last())">
+    <set-variable name="toDate" value="@(context.Request.Url.Query["toDate"].Last())">
 
     <send-request mode="new" response-variable-name="revenuedata" timeout="20" ignore-error="true">
       <set-url>@($"https://accounting.acme.com/salesdata?from={(string)context.Variables["fromDate"]}&to={(string)context.Variables["fromDate"]}")"</set-url>
@@ -249,12 +249,12 @@ The complete policy looks as follows:
     </send-request>
 
     <send-request mode="new" response-variable-name="throughputdata" timeout="20" ignore-error="true">
-    <set-url>@($"https://production.acme.com/throughput?from={(string)context.Variables["fromDate"]}&to={(string)context.Variables["fromDate"]}")"</set-url>
+      <set-url>@($"https://production.acme.com/throughput?from={(string)context.Variables["fromDate"]}&to={(string)context.Variables["fromDate"]}")"</set-url>
       <set-method>GET</set-method>
     </send-request>
 
     <send-request mode="new" response-variable-name="accidentdata" timeout="20" ignore-error="true">
-    <set-url>@($"https://production.acme.com/accidentdata?from={(string)context.Variables["fromDate"]}&to={(string)context.Variables["fromDate"]}")"</set-url>
+      <set-url>@($"https://production.acme.com/accidentdata?from={(string)context.Variables["fromDate"]}&to={(string)context.Variables["fromDate"]}")"</set-url>
       <set-method>GET</set-method>
     </send-request>
 
@@ -268,20 +268,18 @@ The complete policy looks as follows:
                       new JProperty("materialdata",((IResponse)context.Variables["materialdata"]).Body.As<JObject>()),
                       new JProperty("throughputdata",((IResponse)context.Variables["throughputdata"]).Body.As<JObject>()),
                       new JProperty("accidentdata",((IResponse)context.Variables["accidentdata"]).Body.As<JObject>())
-                      ).ToString())
+        ).ToString())
       </set-body>
     </return-response>
-    </inbound>
-    <backend>
-        <base />
-    </backend>
-    <outbound>
-        <base />
-    </outbound>
+  </inbound>
+  <backend>
+    <base />
+  </backend>
+  <outbound>
+    <base />
+  </outbound>
 </policies>
 ```
 
-In the configuration of the placeholder operation, you can configure the dashboard resource to be cached for at least an hour. 
-
 ## Summary
 Azure API Management service provides flexible policies that can be selectively applied to HTTP traffic and enables composition of backend services. Whether you want to enhance your API gateway with alerting functions, verification, validation capabilities or create new composite resources based on multiple backend services, the `send-request` and related policies open a world of possibilities.

articles/active-directory-domain-services/media/tutorial-create-management-vm/delete-user-all-users-blade.png

@@ -5,10 +5,16 @@ ms.topic: include
 ms.date: 02/03/2022
 ---
 
-1. Select the Azure icon on the left navigation and expand the subscriptions to find the **coreSqlXYZ** App Service you created previously.
+1. In the Visual Studio Code  terminal, run the .NET CLI command below. This command generates a deployable `publish` folder for the app in the `bin/release/publish` directory.
 
-1. Right-click on the **App Service** node and select **Deploy to Web App**.
+    ```dotnetcli
+    dotnet publish -c Release
+    ```
 
-1. A prompt will appear to select the folder to deploy.  If root of the project is already suggested, choose that option, otherwise select the **Browse** button to select the root folder from the file explorer.
+1. Right-click on the generated `publish` folder in the Visual Studio Code explorer and select **Deploy to Web App**.
 
-When the deployment completes, you should see a VS Code notification prompting you to browse to the deployed app.
+1. A new workflow will open in the command palette at the top of the screen.  Select the subscription you would like to publish your app to.
+
+1. Select the App Service web app you created earlier.
+
+If Visual Studio Code prompts you to confirm, click **deploy**. The deployment process may take a few moments. When the process completes, a notification should appear in the bottom right corner prompting you to browse to the deployed app.