Skip to content

Commit 2223da3

Browse files
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into us1679050bk
2 parents 7eba45a + 76e2f62 commit 2223da3

File tree

210 files changed

+1191
-1013
lines changed

Some content is hidden

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

210 files changed

+1191
-1013
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12529,6 +12529,11 @@
1252912529
"redirect_url": "/azure/blockchain/workbench",
1253012530
"redirect_document_id": false
1253112531
},
12532+
{
12533+
"source_path": "articles/blockchain/service/connect-truffle.md",
12534+
"redirect_url": "/azure/blockchain/service/connect-vscode",
12535+
"redirect_document_id": false
12536+
},
1253212537
{
1253312538
"source_path": "articles/azure-resource-manager/best-practices-resource-manager-security.md",
1253412539
"redirect_url": "/azure/best-practices-network-security",

articles/active-directory-b2c/secure-rest-api.md

Lines changed: 5 additions & 5 deletions
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: conceptual
12-
ms.date: 03/26/2020
12+
ms.date: 03/27/2020
1313
ms.author: mimart
1414
ms.subservice: B2C
1515
---
@@ -215,18 +215,18 @@ A claim provides temporary storage of data during an Azure AD B2C policy executi
215215

216216
### Acquiring an access token
217217

218-
You can obtain an access token in one of several ways: by obtaining it [from a federated identity provider](idp-pass-through-custom.md), by calling a REST API that returns an access token, by using an [ROPC flow](https://docs.microsoft.com/azure/active-directory/develop/v2-oauth-ropc), or by using the [client credentials flow](https://docs.microsoft.com/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow)).
218+
You can obtain an access token in one of several ways: by obtaining it [from a federated identity provider](idp-pass-through-custom.md), by calling a REST API that returns an access token, by using an [ROPC flow](https://docs.microsoft.com/azure/active-directory/develop/v2-oauth-ropc), or by using the [client credentials flow](https://docs.microsoft.com/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow).
219219

220-
The following example uses a REST API technical profile to make a request to the Azure AD token endpoint using the client credentials passed as HTTP basic authentication. To configure this in Azure AD, see [Microsoft identity platform and the OAuth 2.0 client credentials flow](https://docs.microsoft.com/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow).
220+
The following example uses a REST API technical profile to make a request to the Azure AD token endpoint using the client credentials passed as HTTP basic authentication. To configure this in Azure AD, see [Microsoft identity platform and the OAuth 2.0 client credentials flow](https://docs.microsoft.com/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow). You may need to modify this to interface with your Identity Provider.
221221

222-
You may need to modify this to interface with your Identity Provider. See the [RESTful technical profile](restful-technical-profile.md) reference for all options available.
222+
For the ServiceUrl, replace your-tenant-name with the name of your Azure AD tenant. See the [RESTful technical profile](restful-technical-profile.md) reference for all options available.
223223

224224
```xml
225225
<TechnicalProfile Id="SecureREST-AccessToken">
226226
<DisplayName></DisplayName>
227227
<Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.RestfulProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
228228
<Metadata>
229-
<Item Key="ServiceUrl">https://login.microsoftonline.com/microsoft.com/oauth2/v2.0/token</Item>
229+
<Item Key="ServiceUrl">https://login.microsoftonline.com/your-tenant-name.microsoft.com/oauth2/v2.0/token</Item>
230230
<Item Key="AuthenticationType">Basic</Item>
231231
<Item Key="SendClaimsIn">Form</Item>
232232
</Metadata>

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ To correctly work with SSPR writeback, the account specified in Azure AD Connect
5252
* **Reset password**
5353
* **Write permissions** on `lockoutTime`
5454
* **Write permissions** on `pwdLastSet`
55-
* **Extended rights** on either:
55+
* **Extended rights** for "Unexpire Password" on either:
5656
* The root object of *each domain* in that forest
5757
* The user organizational units (OUs) you want to be in scope for SSPR
5858

articles/active-directory/conditional-access/block-legacy-authentication.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: conditional-access
88
ms.topic: conceptual
9-
ms.date: 03/25/2020
9+
ms.date: 03/26/2020
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -73,6 +73,8 @@ The following options are considered legacy authentication protocols
7373
- Reporting Web Services - Used to retrieve report data in Exchange Online.
7474
- Other clients - Other protocols identified as utilizing legacy authentication.
7575

76+
For more information about these authentication protocols and services, see [Sign-in activity reports in the Azure Active Directory portal](../reports-monitoring/concept-sign-ins.md#filter-sign-in-activities).
77+
7678
### Identify legacy authentication use
7779

7880
Before you can block legacy authentication in your directory, you need to first understand if your users have apps that use legacy authentication and how it affects your overall directory. Azure AD sign-in logs can be used to understand if you're using legacy authentication.

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

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: conditional-access
88
ms.topic: conceptual
9-
ms.date: 03/04/2020
9+
ms.date: 03/25/2020
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -64,6 +64,8 @@ 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+
In order to leverage this grant control, Conditional Access requires that the device be registered in Azure Active Directory which requires the use of a broker app. The broker app can be either the Microsoft Authenticator for iOS, or the Microsoft Company portal for Android devices. If a broker app is not installed on the device when the user attempts to authenticate, the user gets redirected to the app store to install the broker app.
68+
6769
This setting applies to the following iOS and Android apps:
6870

6971
- Microsoft Azure Information Protection
@@ -95,12 +97,14 @@ This setting applies to the following iOS and Android apps:
9597
- Microsoft Visio
9698
- Microsoft Word
9799
- Microsoft Yammer
100+
- Microsoft Whiteboard
98101

99102
**Remarks**
100103

101104
- The approved client apps support the Intune mobile application management feature.
102105
- The **Require approved client app** requirement:
103106
- Only supports the iOS and Android for device platform condition.
107+
- A broker app is required to register the device. On iOS, the broker app is Microsoft Authenticator and on Android, it is Intune Company Portal app.
104108
- Conditional Access cannot consider Microsoft Edge in InPrivate mode an approved client app.
105109

106110
See the article, [How to: Require approved client apps for cloud app access with Conditional Access](app-based-conditional-access.md) for configuration examples.
@@ -109,6 +113,8 @@ See the article, [How to: Require approved client apps for cloud app access with
109113

110114
In your Conditional Access policy, you can require an [Intune app protection policy](/intune/app-protection-policy) be present on the client app before access is available to the selected cloud apps.
111115

116+
In order to leverage this grant control, Conditional Access requires that the device be registered in Azure Active Directory which requires the use of a broker app. The broker app can be either the Microsoft Authenticator for iOS, or the Microsoft Company portal for Android devices. If a broker app is not installed on the device when the user attempts to authenticate, the user gets redirected to the app store to install the broker app.
117+
112118
This setting applies to the following client apps:
113119

114120
- Microsoft Cortana
@@ -121,6 +127,7 @@ This setting applies to the following client apps:
121127
- Apps for app protection policy support the Intune mobile application management feature with policy protection.
122128
- The **Require app protection policy** requirements:
123129
- Only supports the iOS and Android for device platform condition.
130+
- A broker app is required to register the device. On iOS, the broker app is Microsoft Authenticator and on Android, it is Intune Company Portal app.
124131

125132
See the article, [How to: Require app protection policy and an approved client app for cloud app access with Conditional Access](app-protection-based-conditional-access.md) for configuration examples.
126133

articles/active-directory/devices/troubleshoot-hybrid-join-windows-current.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -276,7 +276,7 @@ Use Event Viewer logs to locate the error code, suberror code, server error code
276276
- Reason: Connection with the auth endpoint was aborted.
277277
- Resolution: Retry after sometime or try joining from an alternate stable network location.
278278
- **ERROR_ADAL_INTERNET_SECURE_FAILURE** (0xcaa82f8f/-894947441)
279-
- Reason: The Secure Sockets Layer (SSL) certificate sent by the server could not be validated.
279+
- Reason: The Transport Layer Security (TLS), previously known as Secure Sockets Layer (SSL), certificate sent by the server could not be validated.
280280
- Resolution: Check the client time skew. Retry after sometime or try joining from an alternate stable network location.
281281
- **ERROR_ADAL_INTERNET_CANNOT_CONNECT** (0xcaa82efd/-894947587)
282282
- Reason: The attempt to connect to `https://login.microsoftonline.com` failed.

articles/active-directory/hybrid/how-to-connect-install-prerequisites.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -156,17 +156,17 @@ Prior to version 1.1.614.0, Azure AD Connect by default uses TLS 1.0 for encrypt
156156
When using Azure AD Connect to deploy Active Directory Federation Services or the Web Application Proxy, check these requirements:
157157
158158
* If the target server is domain joined, then ensure that Windows Remote Managed is enabled
159-
* In an elevated PSH command window, use command `Enable-PSRemoting –force`
159+
* In an elevated PowerShell command window, use command `Enable-PSRemoting –force`
160160
* If the target server is a non-domain joined WAP machine, then there are a couple of additional requirements
161161
* On the target machine (WAP machine):
162162
* Ensure the winrm (Windows Remote Management / WS-Management) service is running via the Services snap-in
163-
* In an elevated PSH command window, use command `Enable-PSRemoting –force`
163+
* In an elevated PowerShell command window, use command `Enable-PSRemoting –force`
164164
* On the machine on which the wizard is running (if the target machine is non-domain joined or untrusted domain):
165-
* In an elevated PSH command window, use the command `Set-Item WSMan:\localhost\Client\TrustedHosts –Value <DMZServerFQDN> -Force –Concatenate`
165+
* In an elevated PowerShell command window, use the command `Set-Item WSMan:\localhost\Client\TrustedHosts –Value <DMZServerFQDN> -Force –Concatenate`
166166
* In Server Manager:
167167
* add DMZ WAP host to machine pool (server manager -> Manage -> Add Servers...use DNS tab)
168168
* Server Manager All Servers tab: right click WAP server and choose Manage As..., enter local (not domain) creds for the WAP machine
169-
* To validate remote PSH connectivity, in the Server Manager All Servers tab: right click WAP server and choose Windows PowerShell. A remote PSH session should open to ensure remote PowerShell sessions can be established.
169+
* To validate remote PowerShell connectivity, in the Server Manager All Servers tab: right click WAP server and choose Windows PowerShell. A remote PowerShell session should open to ensure remote PowerShell sessions can be established.
170170
171171
### TLS/SSL Certificate Requirements
172172
* It’s strongly recommended to use the same TLS/SSL certificate across all nodes of your AD FS farm and all Web Application proxy servers.

articles/active-directory/user-help/my-apps-portal-end-user-access.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,8 @@ Download and install the extension, based on the browser you're using:
6464

6565
- **Mozilla Firefox** From the **Firefox Add-ons** page, go to the [My Apps Secure Sign-in Extension](https://addons.mozilla.org/firefox/addon/access-panel-extension/) feature, and then select **Add to Firefox**.
6666

67-
- **Microsoft Edge** From the Microsoft Store, go to the [My Apps Secure Sign-in Extension](https://www.microsoft.com/p/my-apps-secure-sign-in-extension/9pc9sckkzk84?rtc=1&activetab=pivot%3Aoverviewtab) feature, and then select **Get**.
67+
- **Microsoft Edge** From the Microsoft Store, go to the [My Apps Secure Sign-in Extension](https://www.microsoft.com/p/my-apps-secure-sign-in-extension/9pc9sckkzk84?rtc=1&activetab=pivot%3Aoverviewtab) feature, and then select **Get** to get the extension for Microsoft Edge legacy browser.
68+
If you are using the new Microsoft Edge browser (Edge on Chromium) then you can get the extenion from [Microsoft Edge Addons Store](https://microsoftedge.microsoft.com/addons/category/EdgeExtensionsEditorsPick).
6869

6970
An icon is added to the right of your **Address** bar, letting you sign-in and customize the extension.
7071

articles/active-directory/users-groups-roles/directory-assign-admin-roles.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ Users in this role can enable, disable, and delete devices in Azure AD and read
134134

135135
### [Compliance Administrator](#compliance-administrator-permissions)
136136

137-
Users with this role have permissions to manage compliance-related features in the Microsoft 365 compliance center, Microsoft 365 admin center, Azure, and Office 365 Security & Compliance Center. Assignees can also manage all features within the Exchange admin center and Teams & Skype for Business admin centers and create support tickets for Azure and Microsoft 365. More information is available at [About Office 365 admin roles](https://support.office.com/article/About-Office-365-admin-roles-da585eea-f576-4f55-a1e0-87090b6aaa9d).
137+
Users with this role have permissions to manage compliance-related features in the Microsoft 365 compliance center, Microsoft 365 admin center, Azure, and Office 365 Security & Compliance Center. Assignees can also create support tickets for Azure and Microsoft 365. More information is available at [About Office 365 admin roles](https://support.office.com/article/About-Office-365-admin-roles-da585eea-f576-4f55-a1e0-87090b6aaa9d).
138138

139139
In | Can do
140140
----- | ----------
@@ -759,10 +759,7 @@ Can read and manage compliance configuration and reports in Azure AD and Office
759759
| microsoft.azure.supportTickets/allEntities/allTasks | Create and manage Azure support tickets. |
760760
| microsoft.office365.webPortal/allEntities/basic/read | Read basic properties on all resources in microsoft.office365.webPortal. |
761761
| microsoft.office365.complianceManager/allEntities/allTasks | Manage all aspects of Office 365 Compliance Manager |
762-
| microsoft.office365.exchange/allEntities/allTasks | Manage all aspects of Exchange Online. |
763762
| microsoft.office365.serviceHealth/allEntities/allTasks | Read and configure Office 365 Service Health. |
764-
| microsoft.office365.sharepoint/allEntities/allTasks | Create and delete all resources, and read and update standard properties in microsoft.office365.sharepoint. |
765-
| microsoft.office365.skypeForBusiness/allEntities/allTasks | Manage all aspects of Skype for Business Online. |
766763
| microsoft.office365.supportTickets/allEntities/allTasks | Create and manage Office 365 support tickets. |
767764

768765
### Compliance Data Administrator permissions
@@ -782,10 +779,7 @@ Creates and manages compliance content.
782779
| microsoft.azure.supportTickets/allEntities/allTasks | Create and manage Azure support tickets. |
783780
| microsoft.office365.webPortal/allEntities/basic/read | Read basic properties on all resources in microsoft.office365.webPortal. |
784781
| microsoft.office365.complianceManager/allEntities/allTasks | Manage all aspects of Office 365 Compliance Manager |
785-
| microsoft.office365.exchange/allEntities/allTasks | Manage all aspects of Exchange Online. |
786782
| microsoft.office365.serviceHealth/allEntities/allTasks | Read and configure Office 365 Service Health. |
787-
| microsoft.office365.sharepoint/allEntities/allTasks | Create and delete all resources, and read and update standard properties in microsoft.office365.sharepoint. |
788-
| microsoft.office365.skypeForBusiness/allEntities/allTasks | Manage all aspects of Skype for Business Online. |
789783
| microsoft.office365.supportTickets/allEntities/allTasks | Create and manage Office 365 support tickets. |
790784

791785
### Conditional Access Administrator permissions

articles/api-management/api-management-howto-mutual-certificates.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ Follow the steps below to upload a new client certificate. If you have not creat
5050
Once the certificate is uploaded, it shows in the **Certificates**. If you have many certificates, make a note of the thumbprint of the desired certificate in order to [Configure an API to use a client certificate for gateway authentication][Configure an API to use a client certificate for gateway authentication].
5151

5252
> [!NOTE]
53-
> To turn off certificate chain validation when using, for example, a self-signed certificate, follow the steps described in this FAQ [item](api-management-faq.md#can-i-use-a-self-signed-ssl-certificate-for-a-back-end).
53+
> To turn off certificate chain validation when using, for example, a self-signed certificate, follow the steps described in this FAQ [item](api-management-faq.md#can-i-use-a-self-signed-tlsssl-certificate-for-a-back-end).
5454
5555
## <a name="step1a"> </a>Delete a client certificate
5656

0 commit comments

Comments
 (0)