Merge pull request #48325 from CelesteDG/celested-aaddev-renameb5

Rename AAD dev docs for pre-Ignite work, batch 5

Author: GitHubber17

.openpublishing.redirection.json

@@ -15460,6 +15460,66 @@
             "redirect_url": "/azure/active-directory/develop/v2-id-and-access-tokens",
             "redirect_document_id": false
         },
+        {
+            "source_path": "articles/active-directory/develop/active-directory-permissions.md",
+            "redirect_url": "/azure/active-directory/develop/v1-permissions-and-consent",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/active-directory-v2-scopes.md",
+            "redirect_url": "/azure/active-directory/develop/v2-permissions-and-consent",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/active-directory-conditional-access-developer.md",
+            "redirect_url": "/azure/active-directory/develop/conditional-access-dev-guide",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/active-directory-v2-compare.md",
+            "redirect_url": "/azure/active-directory/develop/azure-ad-endpoint-comparison",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/active-directory-single-sign-on-protocol-reference.md",
+            "redirect_url": "/azure/active-directory/develop/single-sign-on-saml-protocol",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/active-directory-single-sign-out-protocol-reference.md",
+            "redirect_url": "/azure/active-directory/develop/single-sign-out-saml-protocol",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/active-directory-federation-metadata.md",
+            "redirect_url": "/azure/active-directory/develop/azure-ad-federation-metadata",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/active-directory-branding-guidelines.md",
+            "redirect_url": "/azure/active-directory/develop/howto-add-branding-in-azure-ad-apps",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/active-directory-app-terms-service-privacy-statement.md",
+            "redirect_url": "/azure/active-directory/develop/howto-add-terms-of-service-privacy-statement",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/active-directory-sso-android.md",
+            "redirect_url": "/azure/active-directory/develop/howto-v1-enable-sso-on-android",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/active-directory-sso-ios.md",
+            "redirect_url": "/azure/active-directory/develop/howto-v1-enable-sso-on-ios",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "articles/active-directory/develop/active-directory-saml-debugging.md",
+            "redirect_url": "/azure/active-directory/develop/howto-v1-debug-saml-sso-issues",
+            "redirect_document_id": false
+        },
         {
             "source_path": "articles/virtual-machines/virtual-machines-linux-expand-disks.md",
             "redirect_url": "/azure/virtual-machines/linux/expand-disks",

articles/active-directory/active-directory-apps-index.md

@@ -37,7 +37,7 @@ This section provides quick access to relevant troubleshooting guides. More info
 
 | Feature Area |  |
 |:---:| --- |
-| Federated Single Sign-On |[Troubleshooting SAML-Based Single Sign-On](active-directory-saml-debugging.md) |
+| Federated Single Sign-On |[Troubleshooting SAML-Based Single Sign-On](develop/howto-v1-debug-saml-sso-issues.md) |
 | Password-Based Single Sign-On |[Troubleshooting the Access Panel Extension for Internet Explorer](active-directory-saas-ie-troubleshooting.md) |
 | Application Proxy |[App Proxy Troubleshooting Guide](manage-apps/application-proxy-troubleshoot.md) |
 | Single sign-on between on-prem AD and Azure AD |[Troubleshooting Password Hash Synchronization](connect/active-directory-aadconnectsync-implement-password-hash-synchronization.md#troubleshoot-password-hash-synchronization)<br /><br />[Troubleshooting Password Writeback](authentication/active-directory-passwords-troubleshoot.md#troubleshoot-password-writeback) |
@@ -53,7 +53,7 @@ Single sign-on allows users to access a variety of apps and services using only
 | Thousands of SaaS apps that are pre-integrated with Azure AD with simplified single sign-on configuration steps |[Getting started with the Azure AD application gallery](manage-apps/what-is-single-sign-on.md#get-started-with-the-azure-ad-application-gallery)<br /><br />[Full List of Pre-Integrated Apps that Support Federation](saas-apps/tutorial-list.md)<br /><br />[How to Add Your App to the Azure AD App Gallery](active-directory-app-gallery-listing.md) |
 | More than 150 app tutorials on how to configure single sign-on for apps such as [Salesforce](saas-apps/salesforce-tutorial.md), [ServiceNow](saas-apps/servicenow-tutorial.md), [Google Apps](saas-apps/google-apps-tutorial.md), [Workday](saas-apps/workday-tutorial.md), and many more |[List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory](saas-apps/tutorial-list.md) |
 | How to manually set up and customize your single sign-on configuration |[How to Configure Federated Single Sign-On to Apps that are not in the Azure Active Directory Application Gallery](application-config-sso-how-to-configure-federated-sso-non-gallery.md)<br /><br />[How to Customize Claims Issued in the SAML Token for Pre-Integrated Apps](active-directory-saml-claims-customization.md) |
-| Troubleshooting guide for federated apps that use the SAML protocol |[Troubleshooting SAML-Based Single Sign-On](active-directory-saml-debugging.md) |
+| Troubleshooting guide for federated apps that use the SAML protocol |[Troubleshooting SAML-Based Single Sign-On](develop/howto-v1-debug-saml-sso-issues.md) |
 | How to configure your app's certificate's expiration date, and how to renew your certificates |[Managing Certificates for Federated Single Sign-On in Azure Active Directory](manage-apps/manage-certificates-for-federated-single-sign-on.md) |
 
 Federated single sign-on is available for all editions of Azure AD for up to ten apps per user. [Azure AD Premium](https://azure.microsoft.com/pricing/details/active-directory/) supports unlimited applications. If your organization has [Azure AD Basic](https://azure.microsoft.com/pricing/details/active-directory/) or [Azure AD Premium](https://azure.microsoft.com/pricing/details/active-directory/), then you can [use groups to assign access to federated applications](#managing-access-to-applications).

articles/active-directory/active-directory-saas-custom-apps.md

@@ -144,7 +144,7 @@ Assigning a user will allow Azure AD to issue a token for the user. It also caus
 
 ### Test the SAML application
 
-Before testing the SAML application, you must have set up the application with Azure AD, and assigned users or groups to the application. To test the SAML application, see [How to debug SAML-based single sign-on to applications in Azure Active Directory](develop/active-directory-saml-debugging.md).
+Before testing the SAML application, you must have set up the application with Azure AD, and assigned users or groups to the application. To test the SAML application, see [How to debug SAML-based single sign-on to applications in Azure Active Directory](develop/howto-v1-debug-saml-sso-issues.md).
 
 ## Password single sign-on
 

articles/active-directory/develop/TOC.yml

@@ -70,9 +70,9 @@
   - name: Multi-tenant apps
     href: howto-convert-app-to-be-multi-tenant.md
   - name: Conditional access
-    href: active-directory-conditional-access-developer.md
+    href: conditional-access-dev-guide.md
   - name: Permissions
-    href: active-directory-permissions.md
+    href: v1-permissions-and-consent.md
   - name: OAuth & OpenID Connect
     items:
     - name: OpenID Connect protocol
@@ -89,23 +89,23 @@
     - name: Customize claims
       href: active-directory-saml-claims-customization.md
     - name: Debug SAML-based SSO
-      href: active-directory-saml-debugging.md
+      href: howto-v1-debug-saml-sso-issues.md
     - name: Single sign-on SAML protocol
-      href: active-directory-single-sign-on-protocol-reference.md
+      href: single-sign-on-saml-protocol.md
     - name: Single sign-out SAML protocol
-      href: active-directory-single-sign-out-protocol-reference.md
+      href: single-sign-out-saml-protocol.md
   - name: Create a tenant
     href: quickstart-create-new-tenant.md
   - name: Terms of service and privacy statement
-    href: active-directory-app-terms-service-privacy-statement.md
+    href: howto-add-terms-of-service-privacy-statement.md
   - name: Branding guidelines
-    href: active-directory-branding-guidelines.md
+    href: howto-add-branding-in-azure-ad-apps.md
   - name: Mobile & Desktop SSO
     items:
     - name: Enable SSO on Android
-      href: active-directory-sso-android.md
+      href: howto-v1-enable-sso-on-android.md
     - name: Enable SSO on iOS
-      href: active-directory-sso-ios.md
+      href: howto-v1-enable-sso-on-ios.md
   - name: Azure AD B2B
     href: ../active-directory-b2b-what-is-azure-ad-b2b.md
   - name: User provisioning with SCIM
@@ -169,7 +169,7 @@
     - name: Signing key rollover
       href: active-directory-signing-key-rollover.md
     - name: Federation metadata
-      href: active-directory-federation-metadata.md
+      href: azure-ad-federation-metadata.md
     - name: Certificate credentials
       href: active-directory-certificate-credentials.md
   - name: Application objects
@@ -193,7 +193,7 @@
     - name: Limitations
       href: active-directory-v2-limitations.md
     - name: v1-v2 comparison
-      href: active-directory-v2-compare.md
+      href: azure-ad-endpoint-comparison.md
   - name: Get Started
     items:
     - name: Mobile & Desktop apps
@@ -262,7 +262,7 @@
     - name: Tokens
       href: v2-id-and-access-tokens.md
     - name: Scopes & Consent
-      href: active-directory-v2-scopes.md
+      href: v2-permissions-and-consent.md
 - name: Resources
   items:
   - name: Getting help

articles/active-directory/develop/active-directory-appmodel-v2-overview.md

@@ -44,7 +44,7 @@ Explore in-depth information about the Azure AD v2.0 endpoint platform:
 * [Azure AD v2.0 protocols reference](active-directory-v2-protocols.md)
 * [Azure AD v2.0 tokens reference](v2-id-and-access-tokens.md)
 * [Azure AD v2.0 authentication libraries reference](active-directory-v2-libraries.md)
-* [Scopes and consent in the Azure AD v2.0 endpoint](active-directory-v2-scopes.md)
+* [Scopes and consent in the Azure AD v2.0 endpoint](v2-permissions-and-consent.md)
 * [The Microsoft Graph API](https://graph.microsoft.io)
 
 > [!NOTE]

articles/active-directory/develop/active-directory-authentication-protocols.md

@@ -26,7 +26,7 @@ Azure Active Directory (Azure AD) supports several of the most widely used authe
 ## Authentication Protocols Articles and Reference
 * [Important Information About Signing Key Rollover in Azure AD](active-directory-signing-key-rollover.md) – Learn about Azure AD’s signing key rollover cadence, changes you can make to update the key automatically, and discussion for how to update the most common application scenarios.
 * [Supported Token and Claim Types](v1-id-and-access-tokens.md) - Learn about the claims in the tokens that Azure AD issues.
-* [Federation Metadata](active-directory-federation-metadata.md) - Learn how to find and interpret the metadata documents that Azure AD generates.
+* [Federation Metadata](azure-ad-federation-metadata.md) - Learn how to find and interpret the metadata documents that Azure AD generates.
 * [OAuth 2.0 in Azure AD](v1-protocols-oauth-code.md) - Learn about the implementation of OAuth 2.0 in Azure AD.
 * [OpenID Connect 1.0](v1-protocols-openid-connect-code.md) - Learn how to use OAuth 2.0, an authorization protocol, for authentication.
 * [Service to Service Calls with Client Credentials](v1-oauth2-client-creds-grant-flow.md) - Learn how to use OAuth 2.0 client credentials grant flow for service to service calls.

articles/active-directory/develop/active-directory-protocols-oauth-get-jwt-token.md

@@ -54,7 +54,7 @@ The following headers are required:
 | tenant        | required              | The `{tenant}` value in the path of the request can be used to control who can sign into the application. The allowed values are `common`, `organizations`, `consumers`, and tenant identifiers. For more detail, see [protocol basics](active-directory-v2-protocols.md#endpoints).                                                                                                                                                   |
 | client_id     | required              | The Application ID that the registration portal ([apps.dev.microsoft.com](https://apps.dev.microsoft.com/?referrer=https://azure.microsoft.com/documentation/articles&deeplink=/appList)) assigned your app.                                                                                                                                                                                                                             |
 | grant_type    | required              | Must be `authorization_code` for the authorization code flow.                                                                                                                                                                                                                                                                                                                                                                            |
-| scope         | required              | A space-separated list of scopes. The scopes requested in this leg must be equivalent to or a subset of the scopes in the call to `/authorize`. If the scopes specified in this request span multiple resource server, then the v2.0 endpoint will return a token for the resource specified in the first scope. For a more detailed explanation of scopes, refer to [permissions, consent, and scopes](active-directory-v2-scopes.md). |
+| scope         | required              | A space-separated list of scopes. The scopes requested in this leg must be equivalent to or a subset of the scopes in the call to `/authorize`. If the scopes specified in this request span multiple resource server, then the v2.0 endpoint will return a token for the resource specified in the first scope. For a more detailed explanation of scopes, refer to [permissions, consent, and scopes](v2-permissions-and-consent.md). |
 | code          | required              | The authorization_code that you acquired in the call to `/authorize`                                                                                                                                                                                                                                                                                                                                                                |
 | redirect_uri  | required              | The same redirect_uri value that was used to acquire the authorization_code.                                                                                                                                                                                                                                                                                                                                                             |
 | client_secret | required for web apps | The application secret that you created in the app registration portal for your app. Do not use in a native app, because client_secrets cannot be reliably stored on devices. It is required for web apps and web APIs, which have the ability to store the client_secret securely on the server side.  Client secrets must be URL-encoded before being sent.                                                                                 |

articles/active-directory/develop/active-directory-saml-claims-customization.md

@@ -128,7 +128,7 @@ There are some restricted claims in SAML. If you add these claims, then Azure AD
 ## Next steps
 * [Article Index for Application Management in Azure Active Directory](../active-directory-apps-index.md)
 * [Configuring single sign-on to applications that are not in the Azure Active Directory application gallery](../application-config-sso-how-to-configure-federated-sso-non-gallery.md)
-* [Troubleshooting SAML-Based Single Sign-On](active-directory-saml-debugging.md)
+* [Troubleshooting SAML-Based Single Sign-On](howto-v1-debug-saml-sso-issues.md)
 
 <!--Image references-->
 [1]: ./media/active-directory-saml-claims-customization/user-attribute-section.png

articles/active-directory/develop/active-directory-saml-protocol-reference.md

@@ -21,7 +21,7 @@ ms.reviewer: hirsin, dastrock
 ---
 
 # How Azure Active Directory uses the SAML protocol
-Azure Active Directory (Azure AD) uses the SAML 2.0 protocol to enable applications to provide a single sign-on experience to their users. The [Single Sign-On](active-directory-single-sign-on-protocol-reference.md) and [Single Sign-Out](active-directory-single-sign-out-protocol-reference.md) SAML profiles of Azure AD explain how SAML assertions, protocols, and bindings are used in the identity provider service.
+Azure Active Directory (Azure AD) uses the SAML 2.0 protocol to enable applications to provide a single sign-on experience to their users. The [Single Sign-On](single-sign-on-saml-protocol.md) and [Single Sign-Out](single-sign-out-saml-protocol.md) SAML profiles of Azure AD explain how SAML assertions, protocols, and bindings are used in the identity provider service.
 
 SAML Protocol requires the identity provider (Azure AD) and the service provider (the application) to exchange information about themselves.
 
@@ -36,4 +36,4 @@ Azure Active Directory exposes tenant-specific and common (tenant-independent) s
 * The tenant-independent endpoint is located at
   `https://login.microsoftonline.com/common/FederationMetadata/2007-06/FederationMetadata.xml`. In this endpoint address, **common** appears instead of a tenant domain name or ID.
 
-For information about the federation metadata documents that Azure AD publishes, see [Federation Metadata](active-directory-federation-metadata.md).
+For information about the federation metadata documents that Azure AD publishes, see [Federation Metadata](azure-ad-federation-metadata.md).