Skip to content

Commit 263ade3

Browse files
committed
Merge branch 'master' into release-preview-disk-pools
2 parents 4535994 + da7ab2a commit 263ade3

File tree

170 files changed

+3940
-367
lines changed

Some content is hidden

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

170 files changed

+3940
-367
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14173,6 +14173,11 @@
1417314173
"redirect_url": "/azure/cdn/cdn-create-a-storage-account-with-cdn",
1417414174
"redirect_document_id": false
1417514175
},
14176+
{
14177+
"source_path_from_root": "/articles/cdn/dn-restrict-access-by-country.md",
14178+
"redirect_url": "/azure/cdn/cdn-restrict-access-by-country-region",
14179+
"redirect_document_id": false
14180+
},
1417614181
{
1417714182
"source_path_from_root": "/articles/cdn/cdn-rules-engine.md",
1417814183
"redirect_url": "/azure/cdn/cdn-verizon-premium-rules-engine",

articles/active-directory/enterprise-users/users-bulk-delete.md

Lines changed: 12 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: active-directory
55
author: curtand
66
ms.author: curtand
77
manager: daveba
8-
ms.date: 12/02/2020
8+
ms.date: 07/09/2021
99
ms.topic: how-to
1010
ms.service: active-directory
1111
ms.subservice: enterprise-users
@@ -14,44 +14,33 @@ ms.custom: it-pro
1414
ms.reviewer: jeffsta
1515
ms.collection: M365-identity-device-management
1616
---
17-
1817
# Bulk delete users in Azure Active Directory
1918

20-
Using Azure Active Directory (Azure AD) portal, you can remove a large number of members to a group by using a comma-separated values (CSV) file to bulk delete users.
21-
22-
## Understand the CSV template
19+
Using the Azure Active Directory (Azure AD) portal, you can remove a large number of members to a group by using a comma-separated values (CSV) file to bulk delete users.
2320

24-
Download and fill in the CSV template to help you successfully delete Azure AD users in bulk. The CSV template you download might look like this example:
21+
## CSV template structure
2522

26-
![Spreadsheet for upload and call-outs explaining the purpose and values for each row and column](./media/users-bulk-delete/understand-template.png)
27-
28-
### CSV template structure
23+
![The CSV file contains names and IDs of the users to delete](./media/users-bulk-delete/delete-csv-file.png)
2924

3025
The rows in a downloaded CSV template are as follows:
3126

3227
- **Version number**: The first row containing the version number must be included in the upload CSV.
33-
- **Column headings**: The format of the column headings is <*Item name*> [PropertyName] <*Required or blank*>. For example, `User name [userPrincipalName] Required`. Some older versions of the template might have slight variations.
34-
- **Examples row**: We have included in the template a row of examples of acceptable values for each column. You must remove the examples row and replace it with your own entries.
28+
- **Column headings**: `User name [userPrincipalName] Required`. Older versions of the template might vary.
29+
- **Examples row**: We have included in the template an example of an acceptable value. `Example: [email protected]` You must remove the example row and replace it with your own entries.
3530

3631
### Additional guidance
3732

38-
- The first two rows of the upload template must not be removed or modified, or the upload can't be processed.
33+
- The first two rows of the template must not be removed or modified, or the template can't be processed.
3934
- The required columns are listed first.
40-
- We don't recommend adding new columns to the template. Any additional columns you add are ignored and not processed.
41-
- We recommend that you download the latest version of the CSV template as often as possible.
35+
- Don't add new columns to the template. Any additional columns you add are ignored and not processed.
36+
- Download the latest version of the CSV template before making new changes.
4237

4338
## To bulk delete users
4439

4540
1. [Sign in to your Azure AD organization](https://aad.portal.azure.com) with an account that is a User administrator in the organization.
46-
1. In Azure AD, select **Users** > **Bulk delete**.
47-
1. On the **Bulk delete user** page, select **Download** to receive a valid CSV file of user properties.
48-
49-
![Select a local CSV file in which you list the users you want to delete](./media/users-bulk-delete/bulk-delete.png)
50-
51-
1. Open the CSV file and add a line for each user you want to delete. The only required value is **User principal name**. Then save the file.
52-
53-
![The CSV file contains names and IDs of the users to delete](./media/users-bulk-delete/delete-csv-file.png)
54-
41+
1. In Azure AD, select **Users** > **Bulk operations** > **Bulk delete**.
42+
1. On the **Bulk delete user** page, select **Download** to download the latest version of the CSV template.
43+
1. Open the CSV file and add a line for each user you want to delete. The only required value is **User principal name**. Save the file.
5544
1. On the **Bulk delete user** page, under **Upload your csv file**, browse to the file. When you select the file and click submit, validation of the CSV file starts.
5645
1. When the file contents are validated, you’ll see **File uploaded successfully**. If there are errors, you must fix them before you can submit the job.
5746
1. When your file passes validation, select **Submit** to start the Azure bulk operation that deletes the users.

articles/active-directory/reports-monitoring/howto-integrate-activity-logs-with-log-analytics.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.topic: how-to
1414
ms.tgt_pltfrm: na
1515
ms.workload: identity
1616
ms.subservice: report-monitor
17-
ms.date: 07/02/2021
17+
ms.date: 07/09/2021
1818
ms.author: markvi
1919
ms.reviewer: besiler
2020

@@ -30,6 +30,8 @@ Use the integration of Azure AD activity logs in Azure Monitor logs to perform t
3030
* Compare your Azure AD sign-in logs against security logs published by Azure Security Center.
3131

3232
* Troubleshoot performance bottlenecks on your application’s sign-in page by correlating application performance data from Azure Application Insights.
33+
34+
* Analyze Identity Protection risky users and risk detections logs to detect threats in your environment (public preview)
3335

3436
* Identify sign-ins from applications that use the Active Directory Authentication Library (ADAL) for authentication. [ADAL is nearing end-of-support](../develop/msal-migration.md).
3537

@@ -44,6 +46,8 @@ You can route audit activity logs and sign-in activity logs to Azure Monitor log
4446
* **Audit logs**: The [audit logs activity report](concept-audit-logs.md) gives you access to the history of every task that's performed in your tenant.
4547
* **Sign-in logs**: With the [sign-in activity report](concept-sign-ins.md), you can determine who performed the tasks that are reported in the audit logs.
4648
* **Provisioning logs**: With the [provisioning logs](../app-provisioning/application-provisioning-log-analytics.md), you can monitor which users have been created, updated, and deleted in all your third-party applications.
49+
* **Risky users logs (public preview)**: With the [risky users logs](../identity-protection/howto-identity-protection-investigate-risk.md#risky-users), you can monitor changes in user risk level and remediation activity.
50+
* **Risk detections logs (public preview)**: With the [risk detections logs](../identity-protection/howto-identity-protection-investigate-risk.md#risk-detections), you can monitor user's risk detections and analyze trends in risk activity detected in your organization.
4751

4852
> [!NOTE]
4953
> Azure AD B2C audit and sign-in activity logs are currently unsupported.
@@ -84,6 +88,8 @@ If you want to know for how long the activity data is stored in a Premium tenant
8488
* To send managed identity sign-in logs to the Log Analytics workspace, select the **ManagedIdentitySignInLogs** check box.
8589
* To send provisioning logs to the Log Analytics workspace, select the **ProvisioningLogs** check box.
8690
* To send Active Directory Federation Services (ADFS) sign-in logs to the Log Analytics workspace, select **ADFSSignInLogs**.
91+
* To send risky users logs to the Log Analytics workspace, select the **RiskyUsers** check box. (public preview)
92+
* To send risk detections logs to the Log Analytics workspace, select the **UserRiskEvents** check box. (public preview)
8793

8894
6. Select **Save** to save the setting.
8995

articles/active-directory/user-help/my-applications-portal-workspaces.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Collections are different app views you see in the **My Apps** portal. Apps can
2525
2626
## Access apps using collections
2727

28-
The list of collections in the **My Apps** portal defaults to show one named **All Apps**, which has every app you have access to:
28+
The list of collections in the **My Apps** portal defaults to show one named **Apps**:
2929

3030
![All apps page in the My Apps portal](media/my-applications-portal-workspaces/my-apps-all-apps.png)
3131

@@ -47,4 +47,4 @@ After you organize your apps into the various categories in the **My Apps** port
4747

4848
- [Manage your organizations](my-account-portal-organizations-page.md). Instructions about how to view and manage your organization-related information on the **Organizations** page of the **My Profile** portal.
4949

50-
- [Manage your connected devices](my-account-portal-devices-page.md). Instructions about how to manage the devices you're connected to using your work or school account, on the **Devices** page of the **My Profile** portal.
50+
- [Manage your connected devices](my-account-portal-devices-page.md). Instructions about how to manage the devices you're connected to using your work or school account, on the **Devices** page of the **My Profile** portal.

0 commit comments

Comments
 (0)