Skip to content

Commit 5f39f60

Browse files
authored
Merge pull request #107085 from MicrosoftDocs/master
Merge Master to Live, 4 AM
2 parents 8f4d542 + beba9c4 commit 5f39f60

File tree

178 files changed

+2001
-1014
lines changed

Some content is hidden

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

178 files changed

+2001
-1014
lines changed

articles/active-directory-b2c/saml-issuer-technical-profile.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: celestedg
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 03/09/2020
12+
ms.date: 03/10/2020
1313
ms.author: mimart
1414
ms.subservice: B2C
1515
---
@@ -67,6 +67,12 @@ The CryptographicKeys element contains the following attributes:
6767

6868
To configure the Azure AD B2C SAML sessions between a relying party application, the attribute of the `UseTechnicalProfileForSessionManagement` element, reference to [SamlSSOSessionProvider](custom-policy-reference-sso.md#samlssosessionprovider) SSO session.
6969

70+
## Next steps
71+
72+
See the following article for example of using a SAML issuer technical profile:
73+
74+
- [Register a SAML application in Azure AD B2C](connect-with-saml-service-providers.md)
75+
7076

7177

7278

articles/active-directory/authentication/concept-authentication-methods.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: conceptual
9-
ms.date: 08/16/2019
9+
ms.date: 03/09/2020
1010

1111
ms.author: iainfou
1212
author: iainfoulds
@@ -153,25 +153,25 @@ Users may have a combination of up to five OATH hardware tokens or authenticator
153153

154154
## OATH hardware tokens (public preview)
155155

156-
OATH is an open standard that specifies how one-time password (OTP) codes are generated. Azure AD will support the use of OATH-TOTP SHA-1 tokens of the 30-second or 60-second variety. Customers can procure these tokens from the vendor of their choice. Secret keys are limited to 128 characters, which may not be compatible with all tokens. The secret keys need to be encoded in Base32.
156+
OATH is an open standard that specifies how one-time password (OTP) codes are generated. Azure AD will support the use of OATH-TOTP SHA-1 tokens of the 30-second or 60-second variety. Customers can procure these tokens from the vendor of their choice. Secret keys are limited to 128 characters, which may not be compatible with all tokens. The secret key can only contain the characters *a-z* or *A-Z* and digits *1-7*, and must be encoded in Base32.
157157

158-
![Uploading OATH tokens to the MFA Server OATH tokens blade](media/concept-authentication-methods/mfa-server-oath-tokens-azure-ad.png)
158+
![Uploading OATH tokens to the MFA OATH tokens blade](media/concept-authentication-methods/mfa-server-oath-tokens-azure-ad.png)
159159

160-
OATH hardware tokens are being supported as part of a public preview. For more information about previews, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/)
160+
OATH hardware tokens are supported as part of a public preview. For more information about previews, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/)
161161

162-
Once tokens are acquired they must be uploaded in a comma-separated values (CSV) file format including the UPN, serial number, secret key, time interval, manufacturer, and model as the example below shows.
162+
Once tokens are acquired they must be uploaded in a comma-separated values (CSV) file format including the UPN, serial number, secret key, time interval, manufacturer, and model as shown in the following example:
163163

164164
```csv
165165
upn,serial number,secret key,time interval,manufacturer,model
166-
[email protected],1234567,1234567890abcdef1234567890abcdef,60,Contoso,HardwareKey
166+
[email protected],1234567,1234567abcdef1234567abcdef,60,Contoso,HardwareKey
167167
```
168168

169169
> [!NOTE]
170-
> Make sure you include the header row in your CSV file as shown above.
170+
> Make sure you include the header row in your CSV file.
171171
172-
Once properly formatted as a CSV file, an administrator can then sign in to the Azure portal and navigate to **Azure Active Directory**, **MFA Server**, **OATH tokens**, and upload the resulting CSV file.
172+
Once properly formatted as a CSV file, an administrator can then sign in to the Azure portal, navigate to **Azure Active Directory** > **Security** > **MFA** > **OATH tokens**, and upload the resulting CSV file.
173173

174-
Depending on the size of the CSV file, it may take a few minutes to process. Click the **Refresh** button to get the current status. If there are any errors in the file, you will have the option to download a CSV file listing any errors for you to resolve.
174+
Depending on the size of the CSV file, it may take a few minutes to process. Click the **Refresh** button to get the current status. If there are any errors in the file, you will have the option to download a CSV file listing any errors for you to resolve. The field names in the downloaded CSV file are different than the uploaded version.
175175

176176
Once any errors have been addressed, the administrator then can activate each key by clicking **Activate** for the token to be activated and entering the OTP displayed on the token.
177177

articles/active-directory/authentication/tutorial-enable-sspr-writeback.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,7 @@ To complete this tutorial, you need the following resources and privileges:
4141
* If needed, [complete the previous tutorial to enable Azure AD SSPR](tutorial-enable-sspr.md).
4242
* An existing on-premises AD DS environment configured with a current version of Azure AD Connect.
4343
* If needed, configure Azure AD Connect using the [Express](../hybrid/how-to-connect-install-express.md) or [Custom](../hybrid/how-to-connect-install-custom.md) settings.
44+
* To use Password Writeback, your Domain Controllers must be Windows Server 2008 R2 or later.
4445

4546
## Configure account permissions for Azure AD Connect
4647

articles/active-directory/conditional-access/concept-conditional-access-grant.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ Organizations can choose to use the device identity as part of their Conditional
6464

6565
Organizations can require that an access attempt to the selected cloud apps needs to be made from an approved client app. These approved client apps support [Intune app protection policies](/intune/app-protection-policy) independent of any mobile-device management (MDM) solution.
6666

67-
This setting applies to the following client apps:
67+
This setting applies to the following iOS and Android apps:
6868

6969
- Microsoft Azure Information Protection
7070
- Microsoft Bookings
@@ -77,6 +77,7 @@ This setting applies to the following client apps:
7777
- Microsoft Invoicing
7878
- Microsoft Kaizala
7979
- Microsoft Launcher
80+
- Microsoft Office
8081
- Microsoft OneDrive
8182
- Microsoft OneNote
8283
- Microsoft Outlook

articles/active-directory/governance/entitlement-management-access-package-settings.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ As long as the catalog for the access package is [enabled for external users](en
3939

4040
![Access package overview - My Access portal link](./media/entitlement-management-shared/my-access-portal-link.png)
4141

42-
It is important that you copy the entire My Access portal link when sending it to an internal business partner. This ensures that the partner will get access to your directory's portal to make their request. The link starts with `myaccess`, includes a directory hint, and ends with an access package ID.
42+
It is important that you copy the entire My Access portal link when sending it to an internal business partner. This ensures that the partner will get access to your directory's portal to make their request. The link starts with `myaccess`, includes a directory hint, and ends with an access package ID. (For US Government, the domain in the My Access portal link will be `myaccess.microsoft.us`.)
4343

4444
`https://myaccess.microsoft.com/@<directory_hint>#/access-packages/<access_package_id>`
4545

articles/active-directory/governance/entitlement-management-access-reviews-review-access.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Use the following steps to find and open the access review:
4545

4646
1. Click the **Review user access** link to open the access review.
4747

48-
1. If you don’t have the email, you can find your pending access reviews by navigating directly to https://myaccess.microsoft.com.
48+
1. If you don’t have the email, you can find your pending access reviews by navigating directly to https://myaccess.microsoft.com. (For US Government, use `https://myaccess.microsoft.us` instead.)
4949

5050
1. Click **Access reviews** on the left navigation bar to see a list of pending access reviews assigned to you.
5151

articles/active-directory/governance/entitlement-management-access-reviews-self-review.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ To do an access review, you must first open the access review. Use the following
3535

3636
1. Click the **Review access** link.
3737

38-
1. You can also go directly to https://myaccess.microsoft.com to find your pending access reviews if you don't receive an email.
38+
1. You can also go directly to https://myaccess.microsoft.com to find your pending access reviews if you don't receive an email. (For US Government, use `https://myaccess.microsoft.us` instead.)
3939

4040
1. Click **Access reviews** on the left navigation bar to see a list of pending access reviews assigned to you.
4141

articles/active-directory/governance/entitlement-management-request-access.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The first step is to sign in to the My Access portal where you can request acces
3333

3434
**Prerequisite role:** Requestor
3535

36-
1. Look for an email or a message from the project or business manager you are working with. The email should include a link to the access package you will need access to. The link starts with `myaccess`, includes a directory hint, and ends with an access package ID.
36+
1. Look for an email or a message from the project or business manager you are working with. The email should include a link to the access package you will need access to. The link starts with `myaccess`, includes a directory hint, and ends with an access package ID. (For US Government, the domain may be `https://myaccess.microsoft.us` instead.)
3737

3838
`https://myaccess.microsoft.com/@<directory_hint>#/access-packages/<access_package_id>`
3939

articles/active-directory/governance/entitlement-management-request-approve.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ The first step to approve or deny access requests is to find and open the access
4141

4242
If you don't have the email, you can find the access requests pending your approval by following these steps.
4343

44-
1. Sign in to the My Access portal at [https://myaccess.microsoft.com](https://myaccess.microsoft.com).
44+
1. Sign in to the My Access portal at [https://myaccess.microsoft.com](https://myaccess.microsoft.com). (For US Government, the domain in the My Access portal link will be `myaccess.microsoft.us`.)
4545

4646
1. In the left menu, click **Approvals** to see a list of access requests pending approval.
4747

articles/active-directory/identity-protection/howto-identity-protection-configure-notifications.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,6 @@ Azure AD Identity Protection sends two types of automated notification emails to
2424

2525
This article provides you with an overview of both notification emails.
2626

27-
>[!NOTE]
28-
>Email notifications are available only in the public cloud and are not currently available in the US Government cloud.
29-
3027
## Users at risk detected email
3128

3229
In response to a detected account at risk, Azure AD Identity Protection generates an email alert with **Users at risk detected** as subject. The email includes a link to the **[Users flagged for risk](../reports-monitoring/concept-user-at-risk.md)** report. As a best practice, you should immediately investigate the users at risk.

0 commit comments

Comments
 (0)