Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into rboucher-metrics

Author: rboucher

.openpublishing.redirection.json

@@ -50325,6 +50325,18 @@
         "source_path": "articles/sql-data-warehouse/what-is-a-data-warehouse-unit-dwu-cdwu.md",
         "redirect_url": "/azure/synapse-analytics/sql-data-warehouse/what-is-a-data-warehouse-unit-dwu-cdwu",
         "redirect_document_id": true
+    },
+    {
+      "source_path": "articles/cognitive-services/speech-service/quickstart-voice-assistant-java-android.md",
+      "redirect_url": "/azure/cognitive-services/speech-service/quickstarts/voice-assistants?pivots=programming-language-java&tabs=android"
+    },
+    {
+      "source_path": "articles/cognitive-services/speech-service/quickstart-voice-assistant-java-jre.md",
+      "redirect_url": "/azure/cognitive-services/speech-service/quickstarts/voice-assistants?pivots=programming-language-java&tabs=jre"
+    },
+    {
+      "source_path": "articles/cognitive-services/Speech-Service/quickstart-voice-assistant-csharp-uwp.md",
+      "redirect_url": "/azure/cognitive-services/speech-service/quickstarts/voice-assistants?pivots=programming-language-csharp&tabs=uwp"
     }
   ]
 }

articles/active-directory/app-provisioning/application-provisioning-quarantine-status.md

@@ -34,6 +34,8 @@ There are three ways to check whether an application is in quarantine:
 
   ![Provisioning status bar showing quarantine status](./media/application-provisioning-quarantine-status/progress-bar-quarantined.png)
 
+- In the Azure portal, navigate to **Azure Active Directory** > **Audit Logs** > filter on **Activity: Quarantine** and review the quarantine history. While the view in the progress bar as described above shows whether provisioning is currently in quarantine, the audit logs allow you to see the quarantine history for an application. 
+
 - Use the Microsoft Graph request [Get synchronizationJob](https://docs.microsoft.com/graph/api/synchronization-synchronizationjob-get?view=graph-rest-beta&tabs=http) to programmatically get the status of the provisioning job:
 
         `GET https://graph.microsoft.com/beta/servicePrincipals/{id}/synchronization/jobs/{jobId}/`
@@ -68,4 +70,4 @@ After you've resolved the issue, restart the provisioning job. Certain changes t
 
 - Use Microsoft Graph to [restart the provisioning job](https://docs.microsoft.com/graph/api/synchronization-synchronizationjob-restart?view=graph-rest-beta&tabs=http). You'll have full control over what you restart. You can choose to clear escrows (to restart the escrow counter that accrues toward quarantine status), clear quarantine (to remove the application from quarantine), or clear watermarks. Use the following request:
 
-       `POST /servicePrincipals/{id}/synchronization/jobs/{jobId}/restart`
+       `POST /servicePrincipals/{id}/synchronization/jobs/{jobId}/restart`

articles/active-directory/authentication/concept-authentication-passwordless.md

@@ -57,7 +57,7 @@ Allow your employee's phone to become a passwordless authentication method. You
 
 ![Sign in to Microsoft Edge with the Microsoft Authenticator app](./media/concept-authentication-passwordless/concept-web-sign-in-microsoft-authenticator-app.png)
 
-The Authenticator App turns any iOS or Android phone into a strong, passwordless credential. Users can sign in to any platform or browser by getting a notification to their phone, matching a number displayed on the screen to the one on their phone, and then using their biometric (touch or face) or PIN to confirm.
+The Authenticator App turns any iOS or Android phone into a strong, passwordless credential. Users can sign in to any platform or browser by getting a notification to their phone, matching a number displayed on the screen to the one on their phone, and then using their biometric (touch or face) or PIN to confirm. Please refer to [Download and install the Microsoft Authenticator app](https://docs.microsoft.com/azure/active-directory/user-help/user-help-auth-app-download-install) for installation details.
 
 Passwordless authentication using the Authenticator App follows the same basic pattern as Windows Hello for Business. It's a little more complicated as the user needs to be identified so that Azure AD can find the Microsoft Authenticator App version being used:
 

articles/active-directory/develop/app-registration-portal-training-guide.md

@@ -3,15 +3,15 @@ title: New Azure portal app registration experience
 titleSuffix: Microsoft identity platform
 description: An introduction to the new App registration experience in the Azure portal
 services: active-directory
-author: archieag
+author: mmacy
 manager: CelesteDG
 
 ms.service: active-directory
 ms.subservice: develop
 ms.workload: identity
 ms.topic: conceptual
 ms.date: 11/8/2019
-ms.author: aragra
+ms.author: marsma
 ms.reviewer: lenalepa, alamaral
 ms.custom: aaddev
 ---
@@ -29,7 +29,7 @@ There are many improvements in the new [App registrations](https://go.microsoft.
     check the signed in user in the Azure portal matches the user that
     was signed into the Application registration portal by comparing the
     email address from your profile.
-    > 
+    >
     > In some cases, especially when you sign in using personal Microsoft
     accounts(e.g. Outlook, Live, Xbox, etc.) with an Azure AD email address, we found out that when you
     go to the Azure portal from the old experience, it signs you into a
@@ -129,7 +129,7 @@ desktop). [Learn more](quickstart-configure-app-access-web-apis.md#add-redirect-
 
 Web APIs are configured in Expose an API page.
 
-> [!NOTE] 
+> [!NOTE]
 > Try out the new Authentication settings experience where you can
 configure settings for your application based on the platform or device
 that you want to target. [Learn more](quickstart-configure-app-access-web-apis.md#configure-platform-settings-for-your-application)
@@ -143,8 +143,8 @@ that you want to target. [Learn more](quickstart-configure-app-access-web-apis.m
     Microsoft APIs, APIs my organization uses, or My APIs. The search
     bar on APIs my organization uses tab searches through service
     principals in the tenant.
-    
-    > [!NOTE] 
+
+    > [!NOTE]
     > You won't see this tab if your application isn't
     associated with a tenant. For more info on how to request
     permissions using the new experience, see [this

articles/active-directory/develop/app-registrations-training-guide-for-app-registrations-legacy-users.md

@@ -2,15 +2,15 @@
 title: New Azure portal app registration training guide
 description: Introduces the new Azure portal App registration experience
 services: active-directory
-author: archieag
+author: mmacy
 manager: CelesteDG
 
 ms.service: active-directory
 ms.subservice: develop
 ms.workload: identity
 ms.topic: conceptual
 ms.date: 10/25/2019
-ms.author: aragra
+ms.author: marsma
 ms.reviewer: lenalepa, keyam
 ms.custom: aaddev
 ---

articles/active-directory/develop/reference-aadsts-error-codes.md

@@ -270,6 +270,7 @@ Search on the numeric part of the returned error code.  For example, if you rece
 | AADSTS1000000 | UserNotBoundError - The Bind API requires the Azure AD user to also authenticate with an external IDP, which hasn't happened yet. |
 | AADSTS1000002 | BindCompleteInterruptError - The bind completed successfully, but the user must be informed. |
 | AADSTS7000112 | UnauthorizedClientApplicationDisabled - The application is disabled. |
+| AADSTS7500529 | The value ‘SAMLId-Guid’ is not a valid SAML ID - Azure AD uses this attribute to populate the InResponseTo attribute of the returned response. ID must not begin with a number, so a common strategy is to prepend a string like "id" to the string representation of a GUID. For example, id6c1c178c166d486687be4aaf5e482730 is a valid ID. |
 
 ## Next steps
 

articles/active-directory/reports-monitoring/concept-sign-ins.md

@@ -14,7 +14,7 @@ ms.topic: conceptual
 ms.tgt_pltfrm: na
 ms.workload: identity
 ms.subservice: report-monitor
-ms.date: 02/26/2020
+ms.date: 03/24/2020
 ms.author: markvi
 ms.reviewer: dhanyahk
 
@@ -43,7 +43,11 @@ This article gives you an overview of the sign-ins report.
 
 ### What Azure AD license do you need to access sign-in activity?
 
-* Your tenant must have an Azure AD Premium license associated with it to see the all up sign-in activity report. See [Getting started with Azure Active Directory Premium](../fundamentals/active-directory-get-started-premium.md) to upgrade your Azure Active Directory edition. It will take a couple of days for the data to show up in the reports after you upgrade to a premium license with no data activities before the upgrade.
+- The sign-in activity report is available in all editions of Azure AD.
+
+- If you want to access the sign-in data using an API, your tenant must have an [Azure Active Directory Premium](../fundamentals/active-directory-get-started-premium.md) license associated with it.
+
+
 
 ## Sign-ins report
 

articles/active-directory/reports-monitoring/reference-reports-data-retention.md

@@ -14,7 +14,7 @@ ms.topic: reference
 ms.tgt_pltfrm: 
 ms.workload: identity
 ms.subservice: report-monitor
-ms.date: 11/13/2018
+ms.date: 03/24/2020
 ms.author: markvi
 ms.reviewer: dhanyahk
 
@@ -29,7 +29,7 @@ In this article, you learn about the data retention policies for the different a
 | Azure AD Edition | Collection Start |
 | :--              | :--   |
 | Azure AD Premium P1 <br /> Azure AD Premium P2 | When you sign up for a subscription |
-| Azure AD Free <br /> Azure AD Basic | The first time you open the [Azure Active Directory blade](https://ms.portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview) or use the [reporting APIs](https://aka.ms/aadreports)  |
+| Azure AD Free| The first time you open the [Azure Active Directory blade](https://ms.portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview) or use the [reporting APIs](https://aka.ms/aadreports)  |
 
 ---
 
@@ -62,19 +62,19 @@ For security signals, the collection process starts when you opt-in to use the *
 
 **Activity reports**	
 
-| Report                 | Azure AD Free | Azure AD Basic | Azure AD Premium P1 | Azure AD Premium P2 |
-| :--                    | :--           | :--            | :--                 | :--                 |
-| Audit logs             | 7 days        |  7 days        | 30 days             | 30 days             |
-| Sign-ins               | N/A           |  N/A           | 30 days             | 30 days             |
-| Azure MFA usage        | 30 days       |  30 days       | 30 days             | 30 days             |
+| Report                 | Azure AD Free | Azure AD Premium P1 | Azure AD Premium P2 |
+| :--                    | :--           | :--                 | :--                 |
+| Audit logs             | 7 days        | 30 days             | 30 days             |
+| Sign-ins               | N/A           | 30 days             | 30 days             |
+| Azure MFA usage        | 30 days       | 30 days             | 30 days             |
 
 You can retain the audit and sign-in activity data for longer than the default retention period outlined above by routing it to an Azure storage account using Azure Monitor. For more information, see [Archive Azure AD logs to an Azure storage account](quickstart-azure-monitor-route-logs-to-storage-account.md).
 
 **Security signals**
 
-| Report         | Azure AD Free | Azure AD Basic | Azure AD Premium P1 | Azure AD Premium P2 |
-| :--            | :--           | :--            | :--                 | :--                 |
-| Users at risk  | 7 days        | 7 days         | 30 days             | 90 days             |
-| Risky sign-ins | 7 days        | 7 days         |  30 days            | 90 days             |
+| Report         | Azure AD Free | Azure AD Premium P1 | Azure AD Premium P2 |
+| :--            | :--           | :--                 | :--                 |
+| Users at risk  | 7 days        | 30 days             | 90 days             |
+| Risky sign-ins | 7 days        | 30 days             | 90 days             |
 
 ---