Skip to content

Commit 1906581

Browse files
authored
Merge pull request #161992 from MicrosoftDocs/master
Merge master to live, 4 AM
2 parents e39ad7e + 9e9933f commit 1906581

File tree

139 files changed

+1160
-695
lines changed

Some content is hidden

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

139 files changed

+1160
-695
lines changed

.openpublishing.redirection.json

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14523,6 +14523,11 @@
1452314523
"redirect_url": "/azure/cdn/cdn-verizon-premium-rules-engine",
1452414524
"redirect_document_id": true
1452514525
},
14526+
{
14527+
"source_path_from_root": "/articles/cdn/cdn-troubleshoot-allowed-ca.md",
14528+
"redirect_url": "https://ccadb-public.secure.force.com/microsoft/IncludedCACertificateReportForMSFT",
14529+
"redirect_document_id": false
14530+
},
1452614531
{
1452714532
"source_path_from_root": "/articles/cdn/cdn-rules-engine-reference.md",
1452814533
"redirect_url": "/azure/cdn/cdn-verizon-premium-rules-engine-reference",
@@ -42390,11 +42395,21 @@
4239042395
"redirect_url": "/azure/web-application-firewall/afds/waf-front-door-create-portal",
4239142396
"redirect_document_id": false
4239242397
},
42398+
{
42399+
"source_path_from_root": "/articles/frontdoor/front-door-troubleshoot-allowed-ca.md",
42400+
"redirect_url": "https://ccadb-public.secure.force.com/microsoft/IncludedCACertificateReportForMSFT",
42401+
"redirect_document_id": false
42402+
},
4239342403
{
4239442404
"source_path_from_root": "/articles/frontdoor/waf-front-door-custom-rules.md",
4239542405
"redirect_url": "/azure/web-application-firewall/afds/waf-front-door-custom-rules",
4239642406
"redirect_document_id": false
4239742407
},
42408+
{
42409+
"source_path_from_root": "/articles/frontdoor/standard-premium/troubleshoot-allowed-certificate-authority.md",
42410+
"redirect_url": "https://ccadb-public.secure.force.com/microsoft/IncludedCACertificateReportForMSFT",
42411+
"redirect_document_id": false
42412+
},
4239842413
{
4239942414
"source_path_from_root": "/articles/frontdoor/waf-front-door-custom-rules-powershell.md",
4240042415
"redirect_url": "/azure/web-application-firewall/afds/waf-front-door-custom-rules-powershell",

articles/active-directory-domain-services/join-windows-vm-template.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ If you need a Windows Server VM, you can create and configure one using a Resour
7777

7878
To create a Windows Server VM then join it to a managed domain, complete the following steps:
7979

80-
1. Browse to the [quickstart template](https://azure.microsoft.com/resources/templates/201-vm-domain-join/). Select the option to **Deploy to Azure**.
80+
1. Browse to the [quickstart template](https://azure.microsoft.com/resources/templates/vm-domain-join/). Select the option to **Deploy to Azure**.
8181
1. On the **Custom deployment** page, enter the following information to create and join a Windows Server VM to the managed domain:
8282

8383
| Setting | Value |

articles/active-directory/fundamentals/whats-new.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,19 @@ This page is updated monthly, so revisit it regularly. If you're looking for ite
4444
**Product capability:** User Authentication
4545

4646
Azure AD customers can now easily design and issue verifiable credentials to represent proof of employment, education, or any other claim while respecting privacy. Digitally validate any piece of information about anyone and any business. [Learn more](../verifiable-credentials/index.yml).
47+
48+
---
49+
50+
### Public Preview - Device code flow now includes an app verification prompt
51+
52+
**Type:** New feature
53+
**Service category:** User Authentication
54+
**Product capability:** Authentications (Logins)
4755

56+
As a security improvement, the [device code flow](../develop/v2-oauth2-device-code.md) has been updated to include an additional prompt, which validates that the user is signing into the app they expect. The roll roll out is planned to start in June and expected to be complete by June 30.
57+
58+
To help prevent phishing attacks where an attacker tricks the user into signing into a malicious application, the following prompt is being added: “Are you trying to sign in to [application display name]?". All users will see this prompt while signing in using the device code flow. As a security measure, it cannot be removed or bypassed. [Learn more](../develop/reference-breaking-changes.md#the-device-code-flow-ux-will-now-include-an-app-confirmation-prompt).
59+
4860
---
4961

5062
### Public Preview - build and test expressions for user provisioning
@@ -1111,4 +1123,4 @@ An extra option is now available in the approval process in Entitlement Manageme
11111123

11121124
For more information, go to [Change approval settings for an access package in Azure AD entitlement management](../governance/entitlement-management-access-package-approval-policy.md#alternate-approvers).
11131125

1114-
---
1126+
---
14.8 KB
Loading
6.26 KB
Loading
Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
---
2+
title: Filter your Azure AD audit log
3+
description: In this quickstart, you learn how you can filter entries in your Azure AD audit log.
4+
5+
services: active-directory
6+
ms.service: active-directory
7+
ms.subservice: report-monitor
8+
ms.topic: quickstart
9+
ms.date: 06/11/2021
10+
11+
ms.author: markvi
12+
author: MarkusVi
13+
manager: mtillman
14+
ms.reviewer: besiler
15+
16+
# Customer intent: As an IT admin, you need to know how to filter your audit log so that you can analyze management activities.
17+
18+
ms.collection: M365-identity-device-management
19+
---
20+
# Quickstart: Filter your Azure AD audit log
21+
22+
With the information in the Azure AD audit log, you get access to records of system activities for compliance.
23+
This quickstart shows how to you can locate a newly created user account in your audit log.
24+
25+
26+
## Prerequisites
27+
28+
To complete the scenario in this quickstart, you need:
29+
30+
- **Access to an Azure AD tenant** - If you don't have access to an Azure AD tenant, see [Create your Azure free account today](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
31+
- **A test account called Isabella Simonsen** - If you don't know how to create a test account, see [Add cloud-based users](../fundamentals/add-users-azure-active-directory.md#add-a-new-user).
32+
33+
## Find the new user account
34+
35+
This section provides you with the steps to filter your audit log.
36+
37+
38+
**To find the new user:**
39+
40+
1. Navigate to the [audit log](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Audit).
41+
42+
2. To list only records for Isabella Simonsen:
43+
44+
a. In the toolbar, click **Add filters**.
45+
46+
![Add user filter](./media/quickstart-analyze-sign-in/add-filters.png)
47+
48+
b. In the **Pick a field** list, select **Target**, and then click **Apply**
49+
50+
c. In the **Target** textbox, type the **User Principal Name** of **Isabella Simonsen**, and then click **Apply**.
51+
52+
3. Click the filtered item.
53+
54+
![Filtered items](./media/quickstart-filter-audit-log/audit-log-list.png)
55+
56+
4. Review the **Audit Log Details**.
57+
58+
![Audit log details](./media/quickstart-filter-audit-log/audit-log-details.png)
59+
60+
61+
62+
## Clean up resources
63+
64+
When no longer needed, delete the test user. If you don't know how to delete an Azure AD user, see [Delete users from Azure AD](../fundamentals/add-users-azure-active-directory.md#delete-a-user).
65+
66+
## Next steps
67+
68+
> [!div class="nextstepaction"]
69+
> [What are Azure Active Directory reports?](overview-reports.md)

articles/active-directory/reports-monitoring/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@
1212
- name: Quickstarts
1313
expanded: true
1414
items:
15+
- name: Filter your audit log
16+
href: quickstart-filter-audit-log.md
1517
- name: Analyze sign-ins
1618
href: quickstart-analyze-sign-in.md
1719
- name: Access logs with the Graph API

articles/active-directory/saas-apps/blackboard-learn-shibboleth-tutorial.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.subservice: saas-app-tutorial
1010
ms.workload: identity
1111
ms.topic: tutorial
12-
ms.date: 01/19/2021
12+
ms.date: 06/04/2021
1313
ms.author: jeedes
1414
---
1515
# Tutorial: Azure Active Directory integration with Blackboard Learn - Shibboleth
@@ -31,7 +31,7 @@ To get started, you need the following items:
3131

3232
In this tutorial, you configure and test Azure AD single sign-on in a test environment.
3333

34-
* Blackboard Learn - Shibboleth supports **SP** initiated SSO
34+
* Blackboard Learn - Shibboleth supports **SP** initiated SSO.
3535

3636
## Add Blackboard Learn - Shibboleth from the gallery
3737

@@ -57,7 +57,7 @@ To configure and test Azure AD SSO with Blackboard Learn - Shibboleth, perform t
5757
1. **[Create Blackboard Learn - Shibboleth test user](#create-blackboard-learn---shibboleth-test-user)** - to have a counterpart of B.Simon in Blackboard Learn - Shibboleth that is linked to the Azure AD representation of user.
5858
1. **[Test SSO](#test-sso)** - to verify whether the configuration works.
5959

60-
### Configure Azure AD SSO
60+
## Configure Azure AD SSO
6161

6262
In this section, you enable Azure AD single sign-on in the Azure portal.
6363

@@ -118,15 +118,15 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
118118
1. If you are expecting a role to be assigned to the users, you can select it from the **Select a role** dropdown. If no role has been set up for this app, you see "Default Access" role selected.
119119
1. In the **Add Assignment** dialog, click the **Assign** button.
120120

121-
### Configure Blackboard Learn - Shibboleth SSO
121+
## Configure Blackboard Learn - Shibboleth SSO
122122

123-
To configure single sign-on on **Blackboard Learn - Shibboleth** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Blackboard Learn - Shibboleth support team](https://www.blackboard.com/forms/contact-us_form.aspx). They set this setting to have the SAML SSO connection set properly on both sides.
123+
To configure Blackboard Learn - Shibboleth single sign-on, please refer to this [document](https://help.blackboard.com/Learn/Administrator/SaaS/Authentication/Implement_Authentication/SAML_Authentication_Provider_Type).
124124

125125
### Create Blackboard Learn - Shibboleth test user
126126

127127
In this section, you create a user called Britta Simon in Blackboard Learn - Shibboleth. Work with [Blackboard Learn - Shibboleth support team](https://www.blackboard.com/forms/contact-us_form.aspx) to add the users in the Blackboard Learn - Shibboleth platform. Users must be created and activated before you use single sign-on.
128128

129-
### Test SSO
129+
## Test SSO
130130

131131
In this section, you test your Azure AD single sign-on configuration with following options.
132132

@@ -138,4 +138,4 @@ In this section, you test your Azure AD single sign-on configuration with follow
138138

139139
## Next steps
140140

141-
Once you configure Blackboard Learn - Shibboleth you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Cloud App Security](/cloud-app-security/proxy-deployment-any-app).
141+
Once you configure Blackboard Learn - Shibboleth you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Cloud App Security](/cloud-app-security/proxy-deployment-any-app).

articles/aks/azure-files-csi.md

Lines changed: 1 addition & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -194,36 +194,7 @@ Filesystem
194194

195195
This option is optimized for random access workloads with in-place data updates and provides full POSIX file system support. This section shows you how to use NFS shares with the Azure File CSI driver on an AKS cluster.
196196

197-
Make sure to check the [limitations](../storage/files/storage-files-compare-protocols.md#limitations) and [region availability](../storage/files/storage-files-compare-protocols.md#regional-availability) during the preview phase.
198-
199-
### Register the `AllowNfsFileShares` preview feature
200-
201-
To create a file share that leverages NFS 4.1, you must enable the `AllowNfsFileShares` feature flag on your subscription.
202-
203-
Register the `AllowNfsFileShares` feature flag by using the [az feature register][az-feature-register] command, as shown in the following example:
204-
205-
```azurecli-interactive
206-
az feature register --namespace "Microsoft.Storage" --name "AllowNfsFileShares"
207-
```
208-
209-
It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [az feature list][az-feature-list] command:
210-
211-
```azurecli-interactive
212-
az feature list -o table --query "[?contains(name, 'Microsoft.Storage/AllowNfsFileShares')].{Name:name,State:properties.state}"
213-
```
214-
215-
When ready, refresh the registration of the *Microsoft.Storage* resource provider by using the [az provider register][az-provider-register] command:
216-
217-
```azurecli-interactive
218-
az provider register --namespace Microsoft.Storage
219-
```
220-
221-
### Create a storage account for the NFS file share
222-
223-
[Create a `Premium_LRS` Azure storage account](../storage/files/storage-how-to-create-file-share.md) with following configurations to support NFS shares:
224-
- account kind: FileStorage
225-
- secure transfer required(enable HTTPS traffic only): false
226-
- select the virtual network of your agent nodes in Firewalls and virtual networks - so you might prefer to create the Storage Account in the MC_ resource group.
197+
Make sure to check the [limitations](../storage/files/storage-files-compare-protocols.md#limitations) and [region availability](../storage/files/storage-files-compare-protocols.md#regional-availability).
227198

228199
### Create NFS file share storage class
229200

@@ -236,8 +207,6 @@ metadata:
236207
name: azurefile-csi-nfs
237208
provisioner: file.csi.azure.com
238209
parameters:
239-
resourceGroup: EXISTING_RESOURCE_GROUP_NAME # optional, required only when storage account is not in the same resource group as your agent nodes
240-
storageAccount: EXISTING_STORAGE_ACCOUNT_NAME
241210
protocol: nfs
242211
```
243212

articles/aks/use-ultra-disks.md

Lines changed: 6 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -18,30 +18,6 @@ This feature can only be set at cluster creation or node pool creation time.
1818
> [!IMPORTANT]
1919
> Azure ultra disks require nodepools deployed in availability zones and regions that support these disks as well as only specific VM series. See the [**Ultra disks GA scope and limitations**](../virtual-machines/disks-enable-ultra-ssd.md#ga-scope-and-limitations).
2020
21-
### Register the `EnableUltraSSD` preview feature
22-
23-
To create an AKS cluster or a node pool that can leverage Ultra disks, you must enable the `EnableUltraSSD` feature flag on your subscription.
24-
25-
Register the `EnableUltraSSD` feature flag using the [az feature register][az-feature-register] command as shown in the following example:
26-
27-
```azurecli-interactive
28-
az feature register --namespace "Microsoft.ContainerService" --name "EnableUltraSSD"
29-
```
30-
31-
It takes a few minutes for the status to show *Registered*. You can check on the registration status using the [az feature list][az-feature-list] command:
32-
33-
```azurecli-interactive
34-
az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/EnableUltraSSD')].{Name:name,State:properties.state}"
35-
```
36-
37-
When ready, refresh the registration of the *Microsoft.ContainerService* resource provider using the [az provider register][az-provider-register] command:
38-
39-
```azurecli-interactive
40-
az provider register --namespace Microsoft.ContainerService
41-
```
42-
43-
[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
44-
4521
### Install aks-preview CLI extension
4622

4723
To create an AKS cluster or a node pool that can use Ultra Disks, you need the latest *aks-preview* CLI extension. Install the *aks-preview* Azure CLI extension using the [az extension add][az-extension-add] command, or install any available updates using the [az extension update][az-extension-update] command:
@@ -60,7 +36,7 @@ az extension update --name aks-preview
6036

6137
## Create a new cluster that can use Ultra disks
6238

63-
Create an AKS cluster that is able to leverage Ultra Disks by using the following CLI commands. Use the `--aks-custom-headers` flag to set the `EnableUltraSSD` feature.
39+
Create an AKS cluster that is able to leverage Ultra Disks by using the following CLI commands. Use the `--enable-ultra-ssd` flag to set the `EnableUltraSSD` feature.
6440

6541
Create an Azure resource group:
6642

@@ -73,20 +49,20 @@ Create the AKS cluster with support for Ultra Disks.
7349

7450
```azurecli-interactive
7551
# Create an AKS-managed Azure AD cluster
76-
az aks create -g MyResourceGroup -n MyManagedCluster -l westus2 --node-vm-size Standard_L8s_v2 --zones 1 2 --node-count 2 --aks-custom-headers EnableUltraSSD=true
52+
az aks create -g MyResourceGroup -n MyManagedCluster -l westus2 --node-vm-size Standard_D2s_v3 --zones 1 2 --node-count 2 --enable-ultra-ssd
7753
```
7854

79-
If you want to create clusters without ultra disk support, you can do so by omitting the custom `--aks-custom-headers` parameter.
55+
If you want to create clusters without ultra disk support, you can do so by omitting the `--enable-ultra-ssd` parameter.
8056

8157
## Enable Ultra disks on an existing cluster
8258

83-
You can enable ultra disks on existing clusters by adding a new node pool to your cluster that support ultra disks. Configure a new node pool to use ultra disks by using the `--aks-custom-headers` flag.
59+
You can enable ultra disks on existing clusters by adding a new node pool to your cluster that support ultra disks. Configure a new node pool to use ultra disks by using the `--enable-ultra-ssd` flag.
8460

8561
```azurecli
86-
az aks nodepool add --name ultradisk --cluster-name myAKSCluster --resource-group myResourceGroup --node-vm-size Standard_L8s_v2 --zones 1 2 --node-count 2 --aks-custom-headers EnableUltraSSD=true
62+
az aks nodepool add --name ultradisk --cluster-name myAKSCluster --resource-group myResourceGroup --node-vm-size Standard_D2s_v3 --zones 1 2 --node-count 2 --enable-ultra-ssd
8763
```
8864

89-
If you want to create new node pools without support for ultra disks, you can do so by omitting the custom `--aks-custom-headers` parameter.
65+
If you want to create new node pools without support for ultra disks, you can do so by omitting the `--enable-ultra-ssd` parameter.
9066

9167
## Use ultra disks dynamically with a storage class
9268

0 commit comments

Comments
 (0)