Skip to content

Commit 98042b0

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into heidist-nov1
2 parents 217ec88 + afe5c13 commit 98042b0

File tree

171 files changed

+1723
-1784
lines changed

Some content is hidden

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

171 files changed

+1723
-1784
lines changed

.github/workflows/stale.yml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,8 @@ jobs:
1919
close-pr-label: auto-close
2020
exempt-pr-labels: keep-open
2121
operations-per-run: 1200
22-
ascending: false
22+
ascending: true
23+
start-date: '2020-09-02'
2324
stale-pr-message: >
2425
This pull request has been inactive for at least 14 days.
2526
If you are finished with your changes, don't forget to sign off. See the [contributor guide](https://review.docs.microsoft.com/help/contribute/contribute-how-to-write-pull-request-automation) for instructions.

.openpublishing.redirection.active-directory.json

Lines changed: 28 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10544,6 +10544,33 @@
1054410544
"source_path_from_root": "/articles/active-directory-b2c/troubleshoot-custom-policies.md",
1054510545
"redirect_url": "/azure/active-directory-b2c/troubleshoot",
1054610546
"redirect_document_id": false
10547-
}
10547+
},
10548+
{
10549+
"source_path": "articles/active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-arm.md",
10550+
"redirect_url": "/azure/active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-arm",
10551+
"redirect_document_id": false
10552+
},
10553+
{
10554+
"source_path": "articles/active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-cli.md",
10555+
"redirect_url": "/azure/active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-azcli",
10556+
"redirect_document_id": false
10557+
},
10558+
{
10559+
"source_path": "articles/active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-portal.md",
10560+
"redirect_url": "/azure/active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-azp",
10561+
"redirect_document_id": false
10562+
},
10563+
{
10564+
"source_path": "articles/active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-powershell.md",
10565+
"redirect_url": "/azure/active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-powershell",
10566+
"redirect_document_id": false
10567+
},
10568+
{
10569+
"source_path": "articles/active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-rest.md",
10570+
"redirect_url": "/azure/active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-rest",
10571+
"redirect_document_id": false
10572+
}
10573+
10574+
1054810575
]
1054910576
}

.openpublishing.redirection.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -408,6 +408,16 @@
408408
"redirect_url": "/articles/frontdoor/front-door-quickstart-template-samples",
409409
"redirect_document_id": false
410410
},
411+
{
412+
"source_path_from_root": "/articles/frontdoor/standard-premium/concept-health-probes.md",
413+
"redirect_url": "/articles/frontdoor/front-door-health-probes",
414+
"redirect_document_id": false
415+
},
416+
{
417+
"source_path_from_root": "/articles/frontdoor/standard-premium/concept-ddos.md",
418+
"redirect_url": "/articles/frontdoor/front-door-ddos",
419+
"redirect_document_id": false
420+
},
411421
{
412422
"source_path_from_root": "/articles/azure-sql/database/doc-changes-updates-release-notes.md",
413423
"redirect_url": "/azure/azure-sql/database/doc-changes-updates-release-notes-whats-new",

articles/active-directory/manage-apps/manage-self-service-access.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -21,11 +21,11 @@ ms.reviewer: phsignor
2121

2222
In this article, you learn how to enable self-service application access using the Azure Active Directory Admin Center.
2323

24-
Before your users can self-discover applications from the My Apps portal, you need to enable **Self-service application access** to any applications that you wish to allow users to self-discover and request access to. This functionality is available for applications that were added from the [Azure AD Gallery](./add-application-portal.md), [Azure AD Application Proxy](../app-proxy/application-proxy.md) or were added using [user or admin consent](../develop/application-consent-experience.md).
24+
Before your users can self-discover applications from the [My Apps portal](my-apps-deployment-plan.md), you need to enable **Self-service application access** for the applications. This functionality is available for applications that were added from the Azure AD Gallery, [Azure AD Application Proxy](../app-proxy/application-proxy.md), or were added using [user or admin consent](../develop/application-consent-experience.md).
2525

2626
Using this feature, you can:
2727

28-
- Let users self-discover applications from the [My Apps portal](https://myapps.microsoft.com/) without bothering the IT group.
28+
- Let users self-discover applications from the My Apps portal without bothering the IT group.
2929

3030
- Add those users to a pre-configured group so you can see who has requested access, remove access, and manage the roles assigned to them.
3131

@@ -59,27 +59,27 @@ To enable self-service application access to an application, follow the steps be
5959

6060
1. In the left navigation menu, select **Self-service**.
6161

62-
1. To enable Self-service application access for this application, turn the **Allow users to request access to this application?** toggle to **Yes.**
62+
1. To enable Self-service application access for this application, set **Allow users to request access to this application?** to **Yes.**
6363

6464
1. Next to **To which group should assigned users be added?**, select **Select group**. Choose a group, and then select **Select**. When a user's request is approved, they'll be added to this group. When viewing this group's membership, you'll be able to see who has been granted access to the application through self-service access.
6565

6666
> [!NOTE]
6767
> This setting doesn't support groups synchronized from on-premises.
6868
69-
1. **Optional:** To require business approval before users are allowed access, set the **Require approval before granting access to this application?** toggle to **Yes**.
69+
1. **Optional:** To require business approval before users are allowed access, set **Require approval before granting access to this application?** to **Yes**.
7070

71-
1. **Optional: For applications using password single-sign on only,** to allow business approvers to specify the passwords that are sent to this application for approved users, set the **Allow approvers to set user’s passwords for this application?** toggle to **Yes**.
71+
1. **Optional: For applications using password single-sign on only,** to allow business approvers to specify the passwords that are sent to this application for approved users, set **Allow approvers to set user’s passwords for this application?** to **Yes**.
7272

73-
1. **Optional:** To specify the business approvers who are allowed to approve access to this application, next to **Who is allowed to approve access to this application?**, select **Select approvers**, and then select up to 10 individual business approvers. Then select **Select**.
73+
1. **Optional:** To specify the business approvers who are allowed to approve access to this application, select **Select approvers**, select up to 10 individual business approvers, and then select **Select**.
7474

7575
>[!NOTE]
7676
>Groups are not supported. You can select up to 10 individual business approvers. If you specify multiple approvers, any single approver can approve an access request.
7777
78-
1. **Optional:** **For applications that expose roles**, to assign self-service approved users to a role, next to the **To which role should users be assigned in this application?**, select **Select Role**, and then choose the role to which these users should be assigned. Then select **Select**.
78+
1. **Optional:** **For applications that expose roles**, to assign self-service approved users to a role, select **Select Role**, choose the role to which these users should be assigned, and then select **Select**.
7979

8080
1. Select the **Save** button at the top of the pane to finish.
8181

82-
Once you complete Self-service application configuration, users can navigate to their My Apps portal and select **Add self-service apps** to find the apps that are enabled with self-service access. Business approvers also see a notification in their My Apps portal. You can enable an email notifying them when a user has requested access to an application that requires their approval.
82+
Once you complete self-service application configuration, users can navigate to their My Apps portal and select **Add self-service apps** to find the apps that are enabled with self-service access. Business approvers also see a notification in their My Apps portal. You can enable an email notifying them when a user has requested access to an application that requires their approval.
8383

8484
## Next steps
8585

articles/active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-arm.md

Lines changed: 0 additions & 87 deletions
This file was deleted.

articles/active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-cli.md

Lines changed: 0 additions & 84 deletions
This file was deleted.

0 commit comments

Comments
 (0)