Skip to content

Commit 2fd3a01

Browse files
committed
2 parents a06c648 + e27ea78 commit 2fd3a01

File tree

574 files changed

+5737
-3620
lines changed

Some content is hidden

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

574 files changed

+5737
-3620
lines changed

.openpublishing.publish.config.json

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -931,6 +931,12 @@
931931
"url": "https://github.com/Azure-Samples/cosmos-db-sql-api-dotnet-samples",
932932
"branch": "v3",
933933
"branch_mapping": {}
934+
},
935+
{
936+
"path_to_root": "azure-cosmos-mongodb-dotnet",
937+
"url": "https://github.com/Azure-Samples/cosmos-db-mongodb-api-dotnet-samples",
938+
"branch": "quickstart-test",
939+
"branch_mapping": {}
934940
}
935941
],
936942
"branch_target_mapping": {

.openpublishing.redirection.defender-for-iot.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/defender-for-iot/organizations/plan-network-monitoring.md",
5+
"redirect_url": "/azure/defender-for-iot/organizations/best-practices/plan-network-monitoring",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path_from_root": "/articles/defender-for-iot/organizations/how-to-identify-required-appliances.md",
510
"redirect_url": "/azure/defender-for-iot/organizations/ot-appliance-sizing",

articles/active-directory-domain-services/concepts-forest-trust.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.subservice: domain-services
1010
ms.workload: identity
1111
ms.topic: conceptual
12-
ms.date: 06/07/2021
12+
ms.date: 07/05/2022
1313
ms.author: justinha
1414
---
1515

@@ -280,11 +280,8 @@ Administrators can use *Active Directory Domains and Trusts*, *Netdom* and *Nlte
280280

281281
## Next steps
282282

283-
To learn more about forest trusts, see [How do forest trusts work in Azure AD DS?][concepts-trust]
284-
285283
To get started with creating a managed domain with a forest trust, see [Create and configure an Azure AD DS managed domain][tutorial-create-advanced]. You can then [Create an outbound forest trust to an on-premises domain][create-forest-trust].
286284

287285
<!-- LINKS - INTERNAL -->
288-
[concepts-trust]: concepts-forest-trust.md
289286
[tutorial-create-advanced]: tutorial-create-instance-advanced.md
290287
[create-forest-trust]: tutorial-create-forest-trust.md

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

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -80,10 +80,11 @@ After the first failure, the first retry happens within the next 2 hours (usuall
8080
- The third retry happens 12 hours after the first failure.
8181
- The fourth retry happens 24 hours after the first failure.
8282
- The fifth retry happens 48 hours after the first failure.
83-
- The sixth retry happens 96 hours after the first failure
84-
- The seventh retry happens 168 hours after the first failure.
83+
- The sixth retry happens 72 hours after the first failure.
84+
- The seventh retry happens 96 hours after the first failure.
85+
- The eigth retry happens 120 hours after the first failure.
8586

86-
After the 7th failure, entry is flagged and no further retries are run.
87+
This cycle is repeated every 24 hours until the 30th day when retries are stopped and the job is disabled.
8788

8889

8990
## How do I get my application out of quarantine?
71.5 KB
Loading
105 KB
Loading

articles/active-directory/app-provisioning/on-premises-scim-provisioning.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: active-directory
77
ms.subservice: app-provisioning
88
ms.topic: conceptual
99
ms.workload: identity
10-
ms.date: 11/17/2021
10+
ms.date: 07/05/2022
1111
ms.author: billmath
1212
ms.reviewer: arvinh
1313
---
@@ -27,7 +27,6 @@ The Azure Active Directory (Azure AD) provisioning service supports a [SCIM 2.0]
2727
To provision users to SCIM-enabled apps:
2828

2929
1. [Download](https://aka.ms/OnPremProvisioningAgent) the provisioning agent and copy it onto the virtual machine or server that your SCIM endpoint is hosted on.
30-
1. Copy the agent onto the virtual machine or server that your SCIM endpoint is hosted on.
3130
1. Open the provisioning agent installer, agree to the terms of service, and select **Install**.
3231
1. Open the provisioning agent wizard, and select **On-premises provisioning** when prompted for the extension you want to enable.
3332
1. Provide credentials for an Azure AD administrator when you're prompted to authorize. Hybrid administrator or global administrator is required.

articles/active-directory/app-provisioning/provision-on-demand.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Provision a user on demand by using Azure Active Directory
2+
title: Provision a user or group on demand using the Azure Active Directory provisioning service
33
description: Learn how to provision users on demand in Azure Active Directory.
44
services: active-directory
55
author: kenwith
@@ -8,13 +8,13 @@ ms.service: active-directory
88
ms.subservice: app-provisioning
99
ms.workload: identity
1010
ms.topic: how-to
11-
ms.date: 03/09/2022
11+
ms.date: 07/06/2022
1212
ms.author: kenwith
1313
ms.reviewer: arvinh
1414
---
1515

1616
# On-demand provisioning in Azure Active Directory
17-
Use on-demand provisioning to provision a user into an application in seconds. Among other things, you can use this capability to:
17+
Use on-demand provisioning to provision a user or group in seconds. Among other things, you can use this capability to:
1818

1919
* Troubleshoot configuration issues quickly.
2020
* Validate expressions that you've defined.
@@ -27,15 +27,16 @@ Use on-demand provisioning to provision a user into an application in seconds. A
2727
1. Select your application, and then go to the provisioning configuration page.
2828
1. Configure provisioning by providing your admin credentials.
2929
1. Select **Provision on demand**.
30-
1. Search for a user by first name, last name, display name, user principal name, or email address.
30+
1. Search for a user by first name, last name, display name, user principal name, or email address. Alternatively, you can search for a group and pick up to 5 users.
3131
> [!NOTE]
3232
> For Cloud HR provisioning app (Workday/SuccessFactors to AD/Azure AD), the input value is different.
3333
> For Workday scenario, please provide "WorkerID" or "WID" of the user in Workday.
3434
> For SuccessFactors scenario, please provide "personIdExternal" of the user in SuccessFactors.
3535
3636
1. Select **Provision** at the bottom of the page.
3737

38-
:::image type="content" source="media/provision-on-demand/on-demand-provision-user.jpg" alt-text="Screenshot that shows the Azure portal UI for provisioning a user on demand.":::
38+
:::image type="content" source="media/provision-on-demand/on-demand-provision-user.png" alt-text="Screenshot that shows the Azure portal UI for provisioning a user on demand." lightbox="media/provision-on-demand/on-demand-provision-user.png":::
39+
3940

4041
## Understand the provisioning steps
4142

@@ -121,7 +122,7 @@ Finally, the provisioning service takes an action, such as creating, updating, d
121122

122123
Here's an example of what you might see after the successful on-demand provisioning of a user:
123124

124-
:::image type="content" source="media/provision-on-demand/success-on-demand-provision.jpg" alt-text="Screenshot that shows the successful on-demand provisioning of a user.":::
125+
:::image type="content" source="media/provision-on-demand/success-on-demand-provision.png" alt-text="Screenshot that shows the successful on-demand provisioning of a user." lightbox="media/provision-on-demand/success-on-demand-provision.png":::
125126

126127
#### View details
127128

@@ -130,6 +131,7 @@ The **View details** section displays the attributes that were modified in the t
130131
#### Troubleshooting tips
131132

132133
* Failures for exporting changes can vary greatly. Check the [documentation for provisioning logs](../reports-monitoring/concept-provisioning-logs.md#error-codes) for common failures.
134+
* On-demand provisioning says the group or user can't be provisioned because they're not assigned to the application. Note that there is a replicate delay of up to a few minutes between when an object is assigned to an application and that assignment being honored by on-demand provisioning. You may need to wait a few minutes and try again.
133135

134136
## Frequently asked questions
135137

@@ -144,10 +146,9 @@ There are currently a few known limitations to on-demand provisioning. Post your
144146
> [!NOTE]
145147
> The following limitations are specific to the on-demand provisioning capability. For information about whether an application supports provisioning groups, deletions, or other capabilities, check the tutorial for that application.
146148
147-
* Amazon Web Services (AWS) application does not support on-demand provisioning.
148-
* On-demand provisioning of groups and roles isn't supported.
149+
* On-demand provisioning of groups supports updating up to 5 members at a time
150+
* On-demand provisioning of roles isn't supported.
149151
* On-demand provisioning supports disabling users that have been unassigned from the application. However, it doesn't support disabling or deleting users that have been disabled or deleted from Azure AD. Those users won't appear when you search for a user.
150-
* Provisioning multiple roles on a user isn't supported by on-demand provisioning.
151152

152153
## Next steps
153154

articles/active-directory/cloud-infrastructure-entitlement-management/onboard-aws.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,11 +18,6 @@ This article describes how to onboard an Amazon Web Services (AWS) account on Pe
1818
> [!NOTE]
1919
> A *global administrator* or *super admin* (an admin for all authorization system types) can perform the tasks in this article after the global administrator has initially completed the steps provided in [Enable Permissions Management on your Azure Active Directory tenant](onboard-enable-tenant.md).
2020
21-
22-
## View a training video on configuring and onboarding an AWS account
23-
24-
To view a video on how to configure and onboard AWS accounts in Permissions Management, select [Configure and onboard AWS accounts](https://www.youtube.com/watch?v=R6K21wiWYmE).
25-
2621
## Onboard an AWS account
2722

2823
1. If the **Data Collectors** dashboard isn't displayed when Permissions Management launches:

articles/active-directory/cloud-infrastructure-entitlement-management/onboard-azure.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -24,11 +24,6 @@ To add Permissions Management to your Azure AD tenant:
2424
- You must have an Azure AD user account and an Azure command-line interface (Azure CLI) on your system, or an Azure subscription. If you don't already have one, [create a free account](https://azure.microsoft.com/free/).
2525
- You must have **Microsoft.Authorization/roleAssignments/write** permission at the subscription or management group scope to perform these tasks. If you don't have this permission, you can ask someone who has this permission to perform these tasks for you.
2626

27-
28-
## View a training video on enabling Permissions Management in your Azure AD tenant
29-
30-
To view a video on how to enable Permissions Management in your Azure AD tenant, select [Enable Permissions Management in your Azure AD tenant](https://www.youtube.com/watch?v=-fkfeZyevoo).
31-
3227
## How to onboard an Azure subscription
3328

3429
1. If the **Data Collectors** dashboard isn't displayed when Permissions Management launches:

0 commit comments

Comments
 (0)