Merge pull request #99731 from MicrosoftDocs/master

12/26 AM Publish

Author: huypub

articles/active-directory/reports-monitoring/reference-powershell-reporting.md

@@ -25,6 +25,13 @@ ms.collection: M365-identity-device-management
 > [!NOTE] 
 > These Powershell cmdlets currently only work with the [Azure AD Preview](https://docs.microsoft.com/powershell/module/azuread/?view=azureadps-2.0-preview#directory_auditing) Module. Please note that the preview module is not suggested for production use. 
 
+To install the public preview release, use the following. 
+
+```powershell
+Install-module AzureADPreview
+```
+For more infromation on how to connect to Azure AD using powershell , please see the article [Azure AD Powershell for Graph](https://docs.microsoft.com/powershell/azure/active-directory/install-adv2?view=azureadps-2.0).  
+
 With Azure Active Directory (Azure AD) reports, you can get details on activities around all the write operations in your direction (audit logs) and authentication data (sign-in logs). Although the information is available by using the MS Graph API, now you can retrieve the same data by using the Azure AD PowerShell cmdlets for reporting.
 
 This article gives you an overview of the PowerShell cmdlets to use for audit logs and sign-in logs.

articles/active-directory/saas-apps/media/workday-inbound-tutorial/wdstudio_aad1.png

@@ -362,19 +362,19 @@ This section provides steps for user account provisioning from Workday to each A
 
 **To configure Workday to Active Directory provisioning:**
 
-1. Go to <https://portal.azure.com>
+1. Go to <https://portal.azure.com>.
 
-2. In the left navigation bar, select **Azure Active Directory**
+2. In the Azure portal, search for and select **Azure Active Directory**.
 
 3. Select **Enterprise Applications**, then **All Applications**.
 
 4. Select **Add an application**, and select the **All** category.
 
 5. Search for **Workday Provisioning to Active Directory**, and add that app from the gallery.
 
-6. After the app is added and the app details screen is shown, select **Provisioning**
+6. After the app is added and the app details screen is shown, select **Provisioning**.
 
-7. Change the **Provisioning** **Mode** to **Automatic**
+7. Change the **Provisioning** **Mode** to **Automatic**.
 
 8. Click on the information banner displayed to download the Provisioning Agent. 
 
@@ -594,17 +594,17 @@ The following sections describe steps for configuring user provisioning from Wor
 
 1. Go to <https://portal.azure.com>.
 
-2. In the left navigation bar, select **Azure Active Directory**
+2. In the Azure portal, search for and select **Azure Active Directory**.
 
 3. Select **Enterprise Applications**, then **All Applications**.
 
 4. Select **Add an application**, and then select the **All** category.
 
 5. Search for **Workday to Azure AD provisioning**, and add that app from the gallery.
 
-6. After the app is added and the app details screen is shown, select **Provisioning**
+6. After the app is added and the app details screen is shown, select **Provisioning**.
 
-7. Change the **Provisioning** **Mode** to **Automatic**
+7. Change the **Provisioning** **Mode** to **Automatic**.
 
 8. Complete the **Admin Credentials** section as follows:
 
@@ -699,19 +699,19 @@ Follow these instructions to configure writeback of user email addresses and use
 
 **To configure Workday Writeback connector:**
 
-1. Go to <https://portal.azure.com>
+1. Go to <https://portal.azure.com>.
 
-2. In the left navigation bar, select **Azure Active Directory**
+2. In the Azure portal, search for and select **Azure Active Directory**.
 
 3. Select **Enterprise Applications**, then **All Applications**.
 
 4. Select **Add an application**, then select the **All** category.
 
 5. Search for **Workday Writeback**, and add that app from the gallery.
 
-6. After the app is added and the app details screen is shown, select **Provisioning**
+6. After the app is added and the app details screen is shown, select **Provisioning**.
 
-7. Change the **Provisioning** **Mode** to **Automatic**
+7. Change the **Provisioning** **Mode** to **Automatic**.
 
 8. Complete the **Admin Credentials** section as follows:
 
@@ -921,7 +921,7 @@ Yes, one Provisioning Agent can be configured to handle multiple AD domains as l
   Get-PublishedResources -TenantId "[tenant ID]"
   ```
 
-* From the list of agents that appear – copy the value of the "id" field from that resource whose *resourceName* equals to your AD domain name.
+* From the list of agents that appear – copy the value of the `id` field from that resource whose *resourceName* equals to your AD domain name.
 * Paste the ID value into this command and execute the command in PowerShell.
 
   ```powershell
@@ -1209,7 +1209,7 @@ This section covers commonly seen errors with Workday user provisioning and how
 |#|Error Scenario |Probable Causes|Recommended Resolution|
 |--|---|---|---|
 |1.| Error installing the provisioning agent with error message:  *Service 'Microsoft Azure AD Connect Provisioning Agent' (AADConnectProvisioningAgent) failed to start. Verify that you have sufficient privileges to start the system.* | This error usually shows up if you are trying to install the provisioning agent on a domain controller and group policy prevents the service from starting.  It is also seen if you have a previous version of the agent running and  you have not uninstalled it before starting a new installation.| Install the provisioning agent on a non-DC server. Ensure that previous versions of the agent are uninstalled before installing the new agent.|
-|2.| The Windows Service 'Microsoft Azure AD Connect Provisioning Agent' is in *Starting* state and does not switch to *Running* state. | As part of the installation, the agent wizard creates a local account (**NT Service\\AADConnectProvisioningAgent**) on the server and this is the **Log On** account used for starting the service. If a security policy on your Windows server prevents local accounts from running the services, you will encounter this error. | Open the *Services console*. Right click on the Windows Service 'Microsoft Azure AD Connect Provisioning Agent' and in the Log On tab specify the account of a domain administrator to run the service. Restart the service. |
+|2.| The Windows Service 'Microsoft Azure AD Connect Provisioning Agent' is in *Starting* state and does not switch to *Running* state. | As part of the installation, the agent wizard creates a local account (**NT Service\\AADConnectProvisioningAgent**) on the server and this is the logon account used for starting the service. If a security policy on your Windows server prevents local accounts from running the services, you will encounter this error. | Open the *Services console*. Right click on the Windows Service 'Microsoft Azure AD Connect Provisioning Agent' and in the logon tab specify the account of a domain administrator to run the service. Restart the service. |
 |3.| When configuring the provisioning agent with your AD domain in the step *Connect Active Directory*, the wizard takes a long time trying to load the AD schema and eventually times out. | This error usually shows up if the wizard is unable to contact the AD domain controller server due to firewall issues. | On the *Connect Active Directory* wizard screen, while providing the credentials for your AD domain, there is an option called *Select domain controller priority*. Use this option to select a domain controller that is in the same site as the agent server and ensure that there are no firewall rules blocking the communication. |
 
 #### Connectivity errors

articles/active-directory/saas-apps/workday-inbound-tutorial.md

@@ -1,19 +1,11 @@
 ---
 title: Azure CLI samples - Azure App Configuration | Microsoft Docs
 description: Provides information about available sample scripts for Azure App Configuration
-services: azure-app-configuration
-documentationcenter: ''
 author: yegu-ms
-manager: balans
-editor: ''
-
+ms.author: yegu
 ms.service: azure-app-configuration
-ms.devlang: na
 ms.topic: sample
-ms.tgt_pltfrm: na
-ms.workload: azure-app-configuration
 ms.date: 02/24/2019
-ms.author: yegu
 ms.custom: mvc
 ---
 

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

@@ -1,18 +1,11 @@
 ---
-title: Azure App Configuration feature management | Microsoft Docs
+title: Azure App Configuration feature management
 description: An overview of how Azure App Configuration can be used to turn on and off application features on demand.
-services: azure-app-configuration
-documentationcenter: ''
 author: yegu-ms
-manager: maiye
-editor: ''
-
+ms.author: yegu
 ms.service: azure-app-configuration
-ms.devlang: na
-ms.topic: overview
-ms.workload: tbd
+ms.topic: conceptual
 ms.date: 04/19/2019
-ms.author: yegu
 ---
 
 # Feature management overview

articles/azure-app-configuration/concept-feature-management.md

@@ -1,18 +1,11 @@
 ---
-title: Azure App Configuration key-value store | Microsoft Docs
-description: An overview of how configuration data is stored in Azure App Configuration
-services: azure-app-configuration
-documentationcenter: ''
+title: Azure App Configuration key-value store
+description: An overview of how configuration data is stored in Azure App Configuration.
 author: yegu-ms
-manager: maiye
-editor: ''
-
+ms.author: yegu
 ms.service: azure-app-configuration
-ms.devlang: na
-ms.topic: overview
-ms.workload: tbd
+ms.topic: conceptual
 ms.date: 04/19/2019
-ms.author: yegu
 ---
 
 # Keys and values

articles/azure-app-configuration/concept-key-value.md

@@ -1,18 +1,12 @@
 ---
-title: Azure App Configuration point-in-time snapshot | Microsoft Docs
+title: Azure App Configuration point-in-time snapshot
 description: An overview of how point-in-time snapshot works in Azure App Configuration
 services: azure-app-configuration
-documentationcenter: ''
 author: yegu-ms
-manager: balans
-editor: ''
-
+ms.author: yegu
 ms.service: azure-app-configuration
-ms.devlang: na
-ms.topic: overview
-ms.workload: tbd
+ms.topic: conceptual
 ms.date: 02/24/2019
-ms.author: yegu
 ---
 
 # Point-in-time snapshot
@@ -23,8 +17,10 @@ Azure App Configuration keeps records of the precise times when a new key-value
 
 To retrieve past key values, specify a time at which key values are snapshot in the HTTP header of a REST API call. For example:
 
-        GET /kv HTTP/1.1
-        Accept-Datetime: Sat, 1 Jan 2019 02:10:00 GMT
+```rest
+GET /kv HTTP/1.1
+Accept-Datetime: Sat, 1 Jan 2019 02:10:00 GMT
+```
 
 Currently, App Configuration keeps seven days of change history.
 

articles/azure-app-configuration/concept-point-time-snapshot.md

@@ -1,19 +1,11 @@
 ---
-title: What is Azure App Configuration? | Microsoft Docs
+title: What is Azure App Configuration?
 description: An overview of the Azure App Configuration service.
-services: azure-app-configuration
-documentationcenter: ''
 author: yegu-ms
-manager: balans
-editor: ''
-
+ms.author: yegu
 ms.service: azure-app-configuration
-ms.workload: tbd
-ms.tgt_pltfrm: na
-ms.devlang: na
 ms.topic: overview
 ms.date: 02/24/2019
-ms.author: yegu
 ---
 
 # What is Azure App Configuration?

articles/azure-app-configuration/overview.md

@@ -1,14 +1,11 @@
 ---
-title: Quickstart to learn how to use Azure App Configuration | Microsoft Docs
+title: Quickstart to learn how to use Azure App Configuration
 description: A quickstart for using Azure App Configuration with Java Spring apps.
-services: azure-app-configuration
 author: yidon
-
-
+ms.author: yidon
 ms.service: azure-app-configuration
 ms.topic: quickstart
 ms.date: 12/17/2019
-ms.author: yidon
 
 #Customer intent: As a Java Spring developer, I want to manage all my app settings in one place.
 ---

articles/azure-app-configuration/quickstart-java-spring-app.md

@@ -124,7 +124,6 @@ The following steps use [APT](https://wiki.debian.org/Apt) to install Core Tools
 
     | Linux distribution | Version |
     | --------------- | ----------- |
-    | Debian 10 | `buster` |
     | Debian 9 | `stretch` |
     | Debian 8 | `jessie` |
     | Ubuntu 18.10    | `cosmic`    |