Skip to content

Commit 615403e

Browse files
authored
Merge pull request #48343 from MicrosoftDocs/master
8/6 PM Publish
2 parents 9819e97 + 2307788 commit 615403e

File tree

285 files changed

+1196
-1192
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

285 files changed

+1196
-1192
lines changed

.openpublishing.redirection.json

Lines changed: 170 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15365,6 +15365,161 @@
1536515365
"redirect_url": "/azure/active-directory/develop/quickstart-v1-openid-connect-code",
1536615366
"redirect_document_id": false
1536715367
},
15368+
{
15369+
"source_path": "articles/active-directory/develop/active-directory-devquickstarts-angular.md",
15370+
"redirect_url": "/azure/active-directory/develop/quickstart-v1-angularjs-spa",
15371+
"redirect_document_id": false
15372+
},
15373+
{
15374+
"source_path": "articles/active-directory/develop/active-directory-devquickstarts-webapi-dotnet.md",
15375+
"redirect_url": "/azure/active-directory/develop/quickstart-v1-dotnet-webapi",
15376+
"redirect_document_id": false
15377+
},
15378+
{
15379+
"source_path": "articles/active-directory/develop/active-directory-devquickstarts-webapi-nodejs.md",
15380+
"redirect_url": "/azure/active-directory/develop/quickstart-v1-nodejs-webapi",
15381+
"redirect_document_id": false
15382+
},
15383+
{
15384+
"source_path": "articles/active-directory/develop/active-directory-v2-code-samples.md",
15385+
"redirect_url": "/azure/active-directory/develop/sample-v2-code",
15386+
"redirect_document_id": false
15387+
},
15388+
{
15389+
"source_path": "articles/active-directory/develop/active-directory-code-samples.md",
15390+
"redirect_url": "/azure/active-directory/develop/sample-v1-code",
15391+
"redirect_document_id": false
15392+
},
15393+
{
15394+
"source_path": "articles/active-directory/develop/active-directory-protocols-oauth-code.md",
15395+
"redirect_url": "/azure/active-directory/develop/v1-protocols-oauth-code",
15396+
"redirect_document_id": false
15397+
},
15398+
{
15399+
"source_path": "articles/active-directory/develop/active-directory-v2-protocols-oidc.md",
15400+
"redirect_url": "/azure/active-directory/develop/v2-protocols-oidc",
15401+
"redirect_document_id": false
15402+
},
15403+
{
15404+
"source_path": "articles/active-directory/develop/active-directory-protocols-openid-connect-code.md",
15405+
"redirect_url": "/azure/active-directory/develop/v1-protocols-openid-connect-code",
15406+
"redirect_document_id": false
15407+
},
15408+
{
15409+
"source_path": "articles/active-directory/develop/active-directory-dev-understanding-oauth2-implicit-grant.md",
15410+
"redirect_url": "/azure/active-directory/develop/v1-oauth2-implicit-grant-flow",
15411+
"redirect_document_id": false
15412+
},
15413+
{
15414+
"source_path": "articles/active-directory/develop/active-directory-v2-protocols-implicit.md",
15415+
"redirect_url": "/azure/active-directory/develop/v2-oauth2-implicit-grant-flow",
15416+
"redirect_document_id": false
15417+
},
15418+
{
15419+
"source_path": "articles/active-directory/develop/active-directory-v2-protocols-oauth-code.md",
15420+
"redirect_url": "/azure/active-directory/develop/v2-oauth2-auth-code-flow",
15421+
"redirect_document_id": false
15422+
},
15423+
{
15424+
"source_path": "articles/active-directory/develop/active-directory-protocols-oauth-on-behalf-of.md",
15425+
"redirect_url": "/azure/active-directory/develop/v1-oauth2-on-behalf-of-flow",
15426+
"redirect_document_id": false
15427+
},
15428+
{
15429+
"source_path": "articles/active-directory/develop/active-directory-v2-protocols-oauth-on-behalf-of.md",
15430+
"redirect_url": "/azure/active-directory/develop/v2-oauth2-on-behalf-of-flow",
15431+
"redirect_document_id": false
15432+
},
15433+
{
15434+
"source_path": "articles/active-directory/develop/active-directory-protocols-oauth-service-to-service.md",
15435+
"redirect_url": "/azure/active-directory/develop/v1-oauth2-client-creds-grant-flow",
15436+
"redirect_document_id": false
15437+
},
15438+
{
15439+
"source_path": "articles/active-directory/develop/active-directory-v2-protocols-oauth-client-creds.md",
15440+
"redirect_url": "/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow",
15441+
"redirect_document_id": false
15442+
},
15443+
{
15444+
"source_path": "articles/active-directory/develop/active-directory-application-objects.md",
15445+
"redirect_url": "/azure/active-directory/develop/app-objects-and-service-principals",
15446+
"redirect_document_id": false
15447+
},
15448+
{
15449+
"source_path": "articles/active-directory/develop/active-directory-devhowto-multi-tenant-overview.md",
15450+
"redirect_url": "/azure/active-directory/develop/howto-convert-app-to-be-multi-tenant",
15451+
"redirect_document_id": false
15452+
},
15453+
{
15454+
"source_path": "articles/active-directory/develop/active-directory-token-and-claims.md",
15455+
"redirect_url": "/azure/active-directory/develop/v1-id-and-access-tokens",
15456+
"redirect_document_id": false
15457+
},
15458+
{
15459+
"source_path": "articles/active-directory/develop/active-directory-v2-tokens.md",
15460+
"redirect_url": "/azure/active-directory/develop/v2-id-and-access-tokens",
15461+
"redirect_document_id": false
15462+
},
15463+
{
15464+
"source_path": "articles/active-directory/develop/active-directory-permissions.md",
15465+
"redirect_url": "/azure/active-directory/develop/v1-permissions-and-consent",
15466+
"redirect_document_id": false
15467+
},
15468+
{
15469+
"source_path": "articles/active-directory/develop/active-directory-v2-scopes.md",
15470+
"redirect_url": "/azure/active-directory/develop/v2-permissions-and-consent",
15471+
"redirect_document_id": false
15472+
},
15473+
{
15474+
"source_path": "articles/active-directory/develop/active-directory-conditional-access-developer.md",
15475+
"redirect_url": "/azure/active-directory/develop/conditional-access-dev-guide",
15476+
"redirect_document_id": false
15477+
},
15478+
{
15479+
"source_path": "articles/active-directory/develop/active-directory-v2-compare.md",
15480+
"redirect_url": "/azure/active-directory/develop/azure-ad-endpoint-comparison",
15481+
"redirect_document_id": false
15482+
},
15483+
{
15484+
"source_path": "articles/active-directory/develop/active-directory-single-sign-on-protocol-reference.md",
15485+
"redirect_url": "/azure/active-directory/develop/single-sign-on-saml-protocol",
15486+
"redirect_document_id": false
15487+
},
15488+
{
15489+
"source_path": "articles/active-directory/develop/active-directory-single-sign-out-protocol-reference.md",
15490+
"redirect_url": "/azure/active-directory/develop/single-sign-out-saml-protocol",
15491+
"redirect_document_id": false
15492+
},
15493+
{
15494+
"source_path": "articles/active-directory/develop/active-directory-federation-metadata.md",
15495+
"redirect_url": "/azure/active-directory/develop/azure-ad-federation-metadata",
15496+
"redirect_document_id": false
15497+
},
15498+
{
15499+
"source_path": "articles/active-directory/develop/active-directory-branding-guidelines.md",
15500+
"redirect_url": "/azure/active-directory/develop/howto-add-branding-in-azure-ad-apps",
15501+
"redirect_document_id": false
15502+
},
15503+
{
15504+
"source_path": "articles/active-directory/develop/active-directory-app-terms-service-privacy-statement.md",
15505+
"redirect_url": "/azure/active-directory/develop/howto-add-terms-of-service-privacy-statement",
15506+
"redirect_document_id": false
15507+
},
15508+
{
15509+
"source_path": "articles/active-directory/develop/active-directory-sso-android.md",
15510+
"redirect_url": "/azure/active-directory/develop/howto-v1-enable-sso-on-android",
15511+
"redirect_document_id": false
15512+
},
15513+
{
15514+
"source_path": "articles/active-directory/develop/active-directory-sso-ios.md",
15515+
"redirect_url": "/azure/active-directory/develop/howto-v1-enable-sso-on-ios",
15516+
"redirect_document_id": false
15517+
},
15518+
{
15519+
"source_path": "articles/active-directory/develop/active-directory-saml-debugging.md",
15520+
"redirect_url": "/azure/active-directory/develop/howto-v1-debug-saml-sso-issues",
15521+
"redirect_document_id": false
15522+
},
1536815523
{
1536915524
"source_path": "articles/virtual-machines/virtual-machines-linux-expand-disks.md",
1537015525
"redirect_url": "/azure/virtual-machines/linux/expand-disks",
@@ -26811,6 +26966,21 @@
2681126966
"source_path": "articles/active-directory/active-directory-conditional-access-whatif.md",
2681226967
"redirect_url": "/azure/active-directory/conditional-access/what-if-tool",
2681326968
"redirect_document_id": true
26969+
},
26970+
{
26971+
"source_path": "articles/active-directory/active-directory-conditional-faqs.md",
26972+
"redirect_url": "/azure/active-directory/conditional-access/faqs",
26973+
"redirect_document_id": true
26974+
},
26975+
{
26976+
"source_path": "articles/active-directory/active-directory-conditional-access-migration.md",
26977+
"redirect_url": "/azure/active-directory/conditional-access/policy-migration",
26978+
"redirect_document_id": true
26979+
},
26980+
{
26981+
"source_path": "articles/active-directory/active-directory-conditional-access-migration-mfa.md",
26982+
"redirect_url": "/azure/active-directory/conditional-access/policy-migration-mfa",
26983+
"redirect_document_id": true
2681426984
}
2681526985
]
2681626986
}

CODEOWNERS

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,3 +5,4 @@
55
# articles/virtual-machines/windows/ @iainfoulds @cynthn
66
# articles/application-insights/ @SergeyKanzhelev
77
# articles/cosmos-db/ @mimig1
8+
articles/cognitive-services/ @nitinme

articles/active-directory-domain-services/active-directory-ds-troubleshoot-service-principals.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ This article helps you troubleshoot and resolve service principal-related config
2626

2727
**Alert message:** *A Service Principal required for Azure AD Domain Services to function properly has been deleted from your Azure AD directory. This configuration impacts Microsoft's ability to monitor, manage, patch, and synchronize your managed domain.*
2828

29-
[Service principals](../active-directory/develop/active-directory-application-objects.md) are applications that Microsoft uses to manage, update, and maintain your managed domain. If they are deleted, it breaks Microsoft's ability to service your domain.
29+
[Service principals](../active-directory/develop/app-objects-and-service-principals.md) are applications that Microsoft uses to manage, update, and maintain your managed domain. If they are deleted, it breaks Microsoft's ability to service your domain.
3030

3131

3232
## Check for missing service principals

articles/active-directory/TOC.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -408,7 +408,7 @@
408408
##### [Require terms of use to be accepted](conditional-access/require-tou.md)
409409
##### [Block access when a session risk is detected](conditional-access/app-sign-in-risk.md)
410410
#### Tutorials
411-
##### [Migrate classic MFA policy](active-directory-conditional-access-migration-mfa.md)
411+
##### [Migrate classic MFA policy](conditional-access/policy-migration-mfa.md)
412412
#### Concepts
413413
##### [Baseline Protection](conditional-access/baseline-protection.md)
414414
##### [Conditions](conditional-access/conditions.md)
@@ -422,12 +422,12 @@
422422
##### [Set up device-based conditional access](active-directory-conditional-access-policy-connected-applications.md)
423423
##### [Set up app-based conditional access](active-directory-conditional-access-mam.md)
424424
##### [Provide terms of use for users and apps](active-directory-tou.md)
425-
##### [Migrate classic policies](active-directory-conditional-access-migration.md)
425+
##### [Migrate classic policies](conditional-access/policy-migration.md)
426426
##### [Set up VPN connectivity](https://docs.microsoft.com/windows-server/remote/remote-access/vpn/always-on-vpn/deploy/always-on-vpn-deploy)
427427
##### [Set up SharePoint and Exchange Online](active-directory-conditional-access-no-modern-authentication.md)
428428
##### [Remediation](active-directory-conditional-access-device-remediation.md)
429429
#### [Technical reference](active-directory-conditional-access-technical-reference.md)
430-
#### [FAQs](active-directory-conditional-faqs.md)
430+
#### [FAQs](conditional-access/faqs.md)
431431

432432
### Certificate-based Authentication
433433
#### [Android](active-directory-certificate-based-authentication-android.md)

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ This section provides quick access to relevant troubleshooting guides. More info
3737

3838
| Feature Area | |
3939
|:---:| --- |
40-
| Federated Single Sign-On |[Troubleshooting SAML-Based Single Sign-On](active-directory-saml-debugging.md) |
40+
| Federated Single Sign-On |[Troubleshooting SAML-Based Single Sign-On](develop/howto-v1-debug-saml-sso-issues.md) |
4141
| Password-Based Single Sign-On |[Troubleshooting the Access Panel Extension for Internet Explorer](active-directory-saas-ie-troubleshooting.md) |
4242
| Application Proxy |[App Proxy Troubleshooting Guide](manage-apps/application-proxy-troubleshoot.md) |
4343
| 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
5353
| 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) |
5454
| 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) |
5555
| 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) |
56-
| Troubleshooting guide for federated apps that use the SAML protocol |[Troubleshooting SAML-Based Single Sign-On](active-directory-saml-debugging.md) |
56+
| Troubleshooting guide for federated apps that use the SAML protocol |[Troubleshooting SAML-Based Single Sign-On](develop/howto-v1-debug-saml-sso-issues.md) |
5757
| 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) |
5858

5959
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-configurable-token-lifetimes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ You can set token lifetime policies for refresh tokens, access tokens, session t
4545
Clients use access tokens to access a protected resource. An access token can be used only for a specific combination of user, client, and resource. Access tokens cannot be revoked and are valid until their expiry. A malicious actor that has obtained an access token can use it for extent of its lifetime. Adjusting the lifetime of an access token is a trade-off between improving system performance and increasing the amount of time that the client retains access after the user’s account is disabled. Improved system performance is achieved by reducing the number of times a client needs to acquire a fresh access token. The default is 1 hour - after 1 hour, the client must use the refresh token to (usually silently) acquire a new refresh token and access token.
4646

4747
### Refresh tokens
48-
When a client acquires an access token to access a protected resource, the client also receives a refresh token. The refresh token is used to obtain new access/refresh token pairs when the current access token expires. A refresh token is bound to a combination of user and client. A refresh token can be [revoked at any time](develop/active-directory-token-and-claims.md#token-revocation), and the token's validity is checked every time the token is used.
48+
When a client acquires an access token to access a protected resource, the client also receives a refresh token. The refresh token is used to obtain new access/refresh token pairs when the current access token expires. A refresh token is bound to a combination of user and client. A refresh token can be [revoked at any time](develop/v1-id-and-access-tokens.md#token-revocation), and the token's validity is checked every time the token is used.
4949

5050
It's important to make a distinction between confidential clients and public clients, as this impacts how long refresh tokens can be used. For more information about different types of clients, see [RFC 6749](https://tools.ietf.org/html/rfc6749#section-2.1).
5151

@@ -103,7 +103,7 @@ You can create and then assign a token lifetime policy to a specific application
103103
* If no policy is explicitly assigned to the service principal or to the organization, the policy assigned to the application is enforced.
104104
* If no policy has been assigned to the service principal, the organization, or the application object, the default values is enforced. (See the table in [Configurable token lifetime properties](#configurable-token-lifetime-properties).)
105105

106-
For more information about the relationship between application objects and service principal objects, see [Application and service principal objects in Azure Active Directory](active-directory-application-objects.md).
106+
For more information about the relationship between application objects and service principal objects, see [Application and service principal objects in Azure Active Directory](develop/app-objects-and-service-principals.md).
107107

108108
A token’s validity is evaluated at the time the token is used. The policy with the highest priority on the application that is being accessed takes effect.
109109

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ Assigning a user will allow Azure AD to issue a token for the user. It also caus
144144
145145
### Test the SAML application
146146
147-
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).
147+
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).
148148
149149
## Password single sign-on
150150

articles/active-directory/conditional-access/best-practices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,7 @@ Consider migrating the policies you have not created in the Azure portal because
145145
- The Azure classic portal has been retired.
146146

147147

148-
For more information, see [Migrate classic policies in the Azure portal](../active-directory-conditional-access-migration.md).
148+
For more information, see [Migrate classic policies in the Azure portal](policy-migration.md).
149149

150150

151151
## Next steps

0 commit comments

Comments
 (0)