Merge pull request #98292 from CelesteDG/celested-metadata-fixes

Batch 2 of metadata fixes

Author: ShannonLeavitt

articles/active-directory/develop/howto-authenticate-service-principal-powershell.md

@@ -3,18 +3,15 @@ title: Create identity for Azure app with PowerShell
 titleSuffix: Microsoft identity platform
 description: Describes how to use Azure PowerShell to create an Azure Active Directory application and service principal, and grant it access to resources through role-based access control. It shows how to authenticate application with a certificate.
 services: active-directory
-documentationcenter: na
 author: rwike77
 manager: CelesteDG
 
 ms.assetid: d2caf121-9fbe-4f00-bf9d-8f3d1f00a6ff
 ms.service: active-directory
 ms.subservice: develop
 ms.custom: aaddev 
-ms.devlang: na
 ms.topic: conceptual
 ms.tgt_pltfrm: multiple
-ms.workload: na
 ms.date: 10/10/2019
 ms.author: ryanwi
 ms.reviewer: tomfitz

articles/active-directory/develop/howto-configure-publisher-domain.md

@@ -3,16 +3,12 @@ title: Configure an application's publisher domain
 titleSuffix: Microsoft identity platform
 description: Learn how to configure an application's publisher domain to let users know where their information is being sent.
 services: active-directory
-documentationcenter: dev-center-name
 author: rwike77
 manager: CelesteDG
-editor: ''
 
 ms.service: active-directory
 ms.subservice: develop
-ms.devlang: na
 ms.topic: conceptual
-ms.tgt_pltfrm: na
 ms.workload: identity
 ms.date: 04/05/2019
 ms.author: ryanwi

articles/active-directory/develop/howto-convert-app-to-be-multi-tenant.md

@@ -3,17 +3,13 @@ title: Build apps that sign in Azure AD users
 titleSuffix: Microsoft identity platform
 description: Shows how to build a multi-tenant application that can sign in a user from any Azure Active Directory tenant.
 services: active-directory
-documentationcenter: ''
 author: rwike77
 manager: CelesteDG
-editor: ''
 
 ms.assetid: 35af95cb-ced3-46ad-b01d-5d2f6fd064a3
 ms.service: active-directory
 ms.subservice: develop
-ms.devlang: na
 ms.topic: conceptual
-ms.tgt_pltfrm: na
 ms.workload: identity
 ms.date: 05/22/2019
 ms.author: ryanwi

articles/active-directory/develop/howto-create-service-principal-portal.md

@@ -3,16 +3,12 @@ title: Create identity for Azure app in portal
 titleSuffix: Microsoft identity platform
 description: Describes how to create a new Azure Active Directory application and service principal that can be used with the role-based access control in Azure Resource Manager to manage access to resources.
 services: active-directory
-documentationcenter: na
 author: rwike77
 manager: CelesteDG
 
 ms.service: active-directory
 ms.subservice: develop
-ms.devlang: na
 ms.topic: conceptual
-ms.tgt_pltfrm: na
-ms.workload: na
 ms.date: 10/14/2019
 ms.author: ryanwi
 ms.reviewer: tomfitz

articles/active-directory/develop/howto-get-appsource-certified.md

@@ -2,21 +2,17 @@
 title: How to get AppSource certified for Azure Active Directory| Microsoft Docs
 description: Details on how to get your application AppSource certified for Azure Active Directory.
 services: active-directory
-documentationcenter: ''
 author: rwike77
 manager: CelesteDG
-editor: ''
 
 ms.assetid: 21206407-49f8-4c0b-84d1-c25e17cd4183
 ms.service: active-directory
 ms.subservice: develop
-ms.devlang: na
 ms.topic: conceptual
-ms.tgt_pltfrm: na
 ms.workload: identity
 ms.date: 08/21/2018
 ms.author: ryanwi
-ms.reviewer: andret
+ms.reviewer: jeedes
 ms.custom: aaddev
 ms.collection: M365-identity-device-management
 ---

articles/active-directory/develop/howto-reactivate-disabled-acs-namespaces.md

@@ -2,15 +2,12 @@
 title: How to reactivate disabled Azure Access Control Service (ACS) namespaces
 description: Learn how to find and enable your Azure Access Control Service (ACS) namespaces and request an extension to keep them enabled until February 4, 2019.
 services: active-directory
-documentationcenter: ''
 author: rwike77
 manager: CelesteDG
 
 ms.service: active-directory
 ms.subservice: develop
 ms.workload: identity
-ms.tgt_pltfrm: na
-ms.devlang: na
 ms.topic: conceptual
 ms.date: 01/21/2019
 ms.author: ryanwi

articles/active-directory/develop/howto-restrict-your-app-to-a-set-of-users.md

@@ -3,20 +3,16 @@ title: Restrict Azure Active Directory-registered app users | Azure
 titleSuffix: Microsoft identity platform
 description: Learn how to restrict access to your apps registered in Azure AD to a selected set of users.
 services: active-directory
-documentationcenter: ''
 author: kalyankrishna1
 manager: CelesteDG
-editor: ''
 
 ms.service: active-directory
 ms.subservice: develop
 ms.workload: identity
-ms.tgt_pltfrm: na
-ms.devlang: na
 ms.topic: conceptual
 ms.date: 09/24/2018
 ms.author: kkrishna
-ms.reviewer: ''
+ms.reviewer: jmprieur
 ms.custom: aaddev
 #Customer intent: As an application developer, I want to restrict an application that I have registered in Azure AD to a select set of users available in my Azure AD tenant
 ms.collection: M365-identity-device-management

articles/active-directory/develop/howto-v1-debug-saml-sso-issues.md

@@ -3,19 +3,16 @@ title: Debug SAML-based single sign-on - Azure Active Directory | Microsoft Docs
 description: Debug SAML-based single sign-on to applications in Azure Active Directory.
 services: active-directory
 author: rwike77
-documentationcenter: na
 manager: CelesteDG
 
 ms.service: active-directory
 ms.subservice: develop
-ms.devlang: na
 ms.topic: conceptual
-ms.tgt_pltfrm: na
 ms.workload: identity
 ms.date: 02/18/2019
 ms.author: ryanwi
 ms.custom: aaddev
-ms.reviewer: luleon, hirsin, smalser
+ms.reviewer: luleon, hirsin, paulgarn
 ms.collection: M365-identity-device-management
 ---
 

articles/active-directory/develop/howto-v1-enable-sso-android.md

@@ -2,7 +2,6 @@
 title: How to enable cross-app SSO on Android using ADAL | Microsoft Docs
 description: How to use the features of the ADAL SDK to enable single sign-on across your applications.
 services: active-directory
-documentationcenter: ''
 author: rwike77
 manager: CelesteDG
 

articles/active-directory/develop/howto-v2-keychain-objc.md

@@ -3,20 +3,16 @@ title: Configure keychain
 titleSuffix: Microsoft identity platform
 description: Learn how to configure keychain so that your app can cache tokens in the keychain.
 services: active-directory
-documentationcenter: ''
 author: TylerMSFT
 manager: CelesteDG
-editor: ''
 
 ms.service: active-directory
 ms.subservice: develop
 ms.workload: identity
-ms.tgt_pltfrm: na
-ms.devlang: na
 ms.topic: conceptual
 ms.date: 08/28/2019
 ms.author: twhitney
-ms.reviewer: ''
+ms.reviewer: oldalton
 ms.custom: aaddev
 ms.collection: M365-identity-device-management
 ---
@@ -47,7 +43,7 @@ On macOS 10.15 onwards (macOS Catalina), MSAL uses keychain access group attribu
 
 If you'd like to use a different keychain access group, you can pass your custom group when creating `MSALPublicClientApplicationConfig` before creating `MSALPublicClientApplication`, like this:
 
-Objective-C:
+# [Objective-C](#tab/objc)
 
 ```objc
 MSALPublicClientApplicationConfig *config = [[MSALPublicClientApplicationConfig alloc] initWithClientId:@"your-client-id"
@@ -63,9 +59,7 @@ MSALPublicClientApplication *application = [[MSALPublicClientApplication alloc]
 // and only shared with other applications declaring the same access group
 ```
 
-
-
-Swift:
+# [Swift](#tab/swift)
 
 ```swift
 let config = MSALPublicClientApplicationConfig(clientId: "your-client-id",
@@ -81,26 +75,28 @@ do {
 }       
 ```
 
-
+---
 
 ## Disable keychain sharing
 
 If you don't want to share SSO state between multiple apps, or use any keychain access group, disable keychain sharing by passing the application bundle ID as your keychainGroup:
 
-Objective-C:
+# [Objective-C](#tab/objc)
 
 ```objc
 config.cacheConfig.keychainSharingGroup = [[NSBundle mainBundle] bundleIdentifier];
 ```
 
-Swift:
+# [Swift](#tab/swift)
 
 ```swift
 if let bundleIdentifier = Bundle.main.bundleIdentifier {
     config.cacheConfig.keychainSharingGroup = bundleIdentifier
 }
 ```
 
+---
+
 ## Handle -34018 error (failed to set item into keychain)
 
 Error -34018 normally means that the keychain hasn't been configured correctly. Ensure the keychain access group that has been configured in MSAL matches the one configured in entitlements.