Skip to content

Commit 068e0a8

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into two-azure-monitor-topics
2 parents 3dfa167 + 84e3dce commit 068e0a8

File tree

394 files changed

+4808
-1920
lines changed

Some content is hidden

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

394 files changed

+4808
-1920
lines changed

.openpublishing.redirection.json

Lines changed: 125 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17255,24 +17255,144 @@
1725517255
"redirect_url": "/azure/security/azure-disk-encryption-linux-powershell-quickstart",
1725617256
"redirect_document_id": false
1725717257
},
17258+
{
17259+
"source_path": "articles/service-bus-relay/diagnostic-logs.md",
17260+
"redirect_url": "/azure/azure-relay/diagnostic-logs",
17261+
"redirect_document_id": false
17262+
},
17263+
{
17264+
"source_path": "articles/service-bus-relay/ip-firewall-virtual-networks.md",
17265+
"redirect_url": "/azure/azure-relay/ip-firewall-virtual-networks",
17266+
"redirect_document_id": false
17267+
},
17268+
{
17269+
"source_path": "articles/service-bus-relay/network-security.md",
17270+
"redirect_url": "/azure/azure-relay/network-security",
17271+
"redirect_document_id": false
17272+
},
17273+
{
17274+
"source_path": "articles/service-bus-relay/private-link-service.md",
17275+
"redirect_url": "/azure/azure-relay/private-link-service",
17276+
"redirect_document_id": false
17277+
},
17278+
{
17279+
"source_path": "articles/service-bus-relay/relay-api-overview.md",
17280+
"redirect_url": "/azure/azure-relay/relay-api-overview",
17281+
"redirect_document_id": false
17282+
},
17283+
{
17284+
"source_path": "articles/service-bus-relay/relay-authentication-and-authorization.md",
17285+
"redirect_url": "/azure/azure-relay/relay-authentication-and-authorization",
17286+
"redirect_document_id": false
17287+
},
17288+
{
17289+
"source_path": "articles/service-bus-relay/relay-create-namespace-portal.md",
17290+
"redirect_url": "/azure/azure-relay/relay-create-namespace-portal",
17291+
"redirect_document_id": false
17292+
},
17293+
{
17294+
"source_path": "articles/service-bus-relay/relay-exceptions.md",
17295+
"redirect_url": "/azure/azure-relay/relay-exceptions",
17296+
"redirect_document_id": false
17297+
},
17298+
{
17299+
"source_path": "articles/service-bus-relay/relay-faq.md",
17300+
"redirect_url": "/azure/azure-relay/relay-faq",
17301+
"redirect_document_id": false
17302+
},
17303+
{
17304+
"source_path": "articles/service-bus-relay/relay-hybrid-connections-dotnet-api-overview.md",
17305+
"redirect_url": "/azure/azure-relay/relay-hybrid-connections-dotnet-api-overview",
17306+
"redirect_document_id": false
17307+
},
17308+
{
17309+
"source_path": "articles/service-bus-relay/relay-hybrid-connections-dotnet-get-started.md",
17310+
"redirect_url": "/azure/azure-relay/relay-hybrid-connections-dotnet-get-started",
17311+
"redirect_document_id": false
17312+
},
17313+
{
17314+
"source_path": "articles/service-bus-relay/relay-hybrid-connections-http-requests-dotnet-get-started.md",
17315+
"redirect_url": "/azure/azure-relay/relay-hybrid-connections-http-requests-dotnet-get-started",
17316+
"redirect_document_id": false
17317+
},
17318+
{
17319+
"source_path": "articles/service-bus-relay/relay-hybrid-connections-http-requests-node-get-started.md",
17320+
"redirect_url": "/azure/azure-relay/relay-hybrid-connections-http-requests-node-get-started",
17321+
"redirect_document_id": false
17322+
},
17323+
{
17324+
"source_path": "articles/service-bus-relay/relay-hybrid-connections-node-get-started.md",
17325+
"redirect_url": "/azure/azure-relay/relay-hybrid-connections-node-get-started",
17326+
"redirect_document_id": false
17327+
},
17328+
{
17329+
"source_path": "articles/service-bus-relay/relay-hybrid-connections-node-ws-api-overview.md",
17330+
"redirect_url": "/azure/azure-relay/relay-hybrid-connections-node-ws-api-overview",
17331+
"redirect_document_id": false
17332+
},
17333+
{
17334+
"source_path": "articles/service-bus-relay/relay-hybrid-connections-protocol.md",
17335+
"redirect_url": "/azure/azure-relay/relay-hybrid-connections-protocol",
17336+
"redirect_document_id": false
17337+
},
17338+
{
17339+
"source_path": "articles/service-bus-relay/relay-metrics-azure-monitor.md",
17340+
"redirect_url": "/azure/azure-relay/relay-metrics-azure-monitor",
17341+
"redirect_document_id": false
17342+
},
17343+
{
17344+
"source_path": "articles/service-bus-relay/relay-migrate-acs-sas.md",
17345+
"redirect_url": "/azure/azure-relay/relay-migrate-acs-sas",
17346+
"redirect_document_id": false
17347+
},
17348+
{
17349+
"source_path": "articles/service-bus-relay/relay-port-settings.md",
17350+
"redirect_url": "/azure/azure-relay/relay-port-settings",
17351+
"redirect_document_id": false
17352+
},
17353+
{
17354+
"source_path": "articles/service-bus-relay/relay-what-is-it.md",
17355+
"redirect_url": "/azure/azure-relay/relay-what-is-it",
17356+
"redirect_document_id": false
17357+
},
17358+
{
17359+
"source_path": "articles/service-bus-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md",
17360+
"redirect_url": "/azure/azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay",
17361+
"redirect_document_id": false
17362+
},
17363+
{
17364+
"source_path": "articles/service-bus-relay/service-bus-relay-rest-tutorial.md",
17365+
"redirect_url": "/azure/azure-relay/service-bus-relay-rest-tutorial",
17366+
"redirect_document_id": false
17367+
},
17368+
{
17369+
"source_path": "articles/service-bus-relay/service-bus-relay-security-controls.md",
17370+
"redirect_url": "/azure/azure-relay/service-bus-relay-security-controls",
17371+
"redirect_document_id": false
17372+
},
17373+
{
17374+
"source_path": "articles/service-bus-relay/service-bus-relay-tutorial.md",
17375+
"redirect_url": "/azure/azure-relay/service-bus-relay-tutorial",
17376+
"redirect_document_id": false
17377+
},
1725817378
{
1725917379
"source_path": "articles/service-bus-relay/relay-wcf-dotnet-get-started.md",
17260-
"redirect_url": "/azure/service-bus-relay/service-bus-relay-tutorial",
17380+
"redirect_url": "/azure/azure-relay/azure-relay-tutorial",
1726117381
"redirect_document_id": false
1726217382
},
1726317383
{
1726417384
"source_path": "articles/service-bus-relay/service-bus-dotnet-how-to-use-relay.md",
17265-
"redirect_url": "/azure/service-bus-relay/relay-wcf-dotnet-get-started",
17385+
"redirect_url": "/azure/azure-relay/relay-wcf-dotnet-get-started",
1726617386
"redirect_document_id": false
1726717387
},
1726817388
{
1726917389
"source_path": "articles/service-bus-relay/service-bus-relay-overview.md",
17270-
"redirect_url": "/azure/service-bus-relay/relay-what-is-it",
17390+
"redirect_url": "/azure/azure-relay/relay-what-is-it",
1727117391
"redirect_document_id": false
1727217392
},
1727317393
{
1727417394
"source_path": "articles/service-bus-relay/service-bus-relay-port-settings.md",
17275-
"redirect_url": "/azure/service-bus-relay/relay-port-settings",
17395+
"redirect_url": "/azure/azure-relay/relay-port-settings",
1727617396
"redirect_document_id": false
1727717397
},
1727817398
{
@@ -32617,7 +32737,7 @@
3261732737
},
3261832738
{
3261932739
"source_path": "articles/service-bus-relay/service-bus-relay-security-attributes.md",
32620-
"redirect_url": "/azure/service-bus-relay/service-bus-relay-security-controls",
32740+
"redirect_url": "/azure/azure-relay/azure-relay-security-controls",
3262132741
"redirect_document_id": false
3262232742
},
3262332743
{

articles/active-directory/authentication/howto-mfa-nps-extension.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,7 @@ manager: daveba
1414
ms.reviewer: michmcla
1515

1616
ms.collection: M365-identity-device-management
17+
ms.custom: has-adal-ref
1718
---
1819
# Integrate your existing NPS infrastructure with Azure Multi-Factor Authentication
1920

articles/active-directory/b2b/add-users-administrator.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ services: active-directory
77
ms.service: active-directory
88
ms.subservice: B2B
99
ms.topic: conceptual
10-
ms.date: 11/12/2019
10+
ms.date: 05/11/2020
1111

1212
ms.author: mimart
1313
author: msmimart
@@ -41,9 +41,6 @@ To add B2B collaboration users to the directory, follow these steps:
4141

4242
![Shows where New guest user is in the UI](./media/add-users-administrator/new-guest-user-in-all-users.png)
4343

44-
> [!NOTE]
45-
> The **New guest user** option is also available on the **Organizational relationships** page. In **Azure Active Directory**, under **Manage**, select **Organizational relationships**.
46-
4744
5. On the **New user** page, select **Invite user** and then add the guest user's information.
4845

4946
> [!NOTE]

articles/active-directory/b2b/auditing-and-reporting.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: B2B
88
ms.topic: conceptual
9-
ms.date: 12/14/2018
9+
ms.date: 05/11/2020
1010

1111
ms.author: mimart
1212
author: msmimart
@@ -20,7 +20,7 @@ ms.collection: M365-identity-device-management
2020
With guest users, you have auditing capabilities similar to with member users.
2121

2222
## Access reviews
23-
You can use access reviews to periodically verify whether guest users still need access to your resources. The **Access reviews** feature is available in **Azure Active Directory** under **Manage** > **Organizational Relationships**. (You can also search for "access reviews" from **All services** in the Azure portal.) To learn how to use access reviews, see [Manage guest access with Azure AD access reviews](../governance/manage-guest-access-with-access-reviews.md).
23+
You can use access reviews to periodically verify whether guest users still need access to your resources. The **Access reviews** feature is available in **Azure Active Directory** under **Organizational Relationships** > **Access reviews** (or **External Identities** > **Access reviews** ). You can also search for "access reviews" from **All services** in the Azure portal. To learn how to use access reviews, see [Manage guest access with Azure AD access reviews](../governance/manage-guest-access-with-access-reviews.md).
2424

2525
## Audit logs
2626

articles/active-directory/b2b/delegate-invitations.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: B2B
88
ms.topic: conceptual
9-
ms.date: 04/11/2019
9+
ms.date: 05/11/2020
1010

1111
ms.author: mimart
1212
author: msmimart
@@ -34,11 +34,9 @@ By default, all users, including guests, can invite guest users.
3434
### To configure external collaboration settings:
3535

3636
1. Sign in to the [Azure portal](https://portal.azure.com) as a tenant administrator.
37-
2. Select **Azure Active Directory** > **Users** > **User settings**.
38-
3. Under **External users**, select **Manage external collaboration settings**.
39-
> [!NOTE]
40-
> The **External collaboration settings** are also available from the **Organizational relationships** page. In Azure Active Directory, under **Manage**, go to **Organizational relationships** > **Settings**.
41-
4. On the **External collaboration settings** page, choose the policies you want to enable.
37+
2. Select **Azure Active Directory**.
38+
3. Select **Organizational Relationships** > **Settings** (or select **External Identities** > **External collaboration settings**).
39+
6. On the **External collaboration settings** page, choose the policies you want to enable.
4240

4341
![External collaboration settings](./media/delegate-invitations/control-who-to-invite.png)
4442

articles/active-directory/b2b/direct-federation.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: B2B
88
ms.topic: conceptual
9-
ms.date: 05/07/2020
9+
ms.date: 05/11/2020
1010

1111
ms.author: mimart
1212
author: msmimart
@@ -143,8 +143,8 @@ Next, you'll configure federation with the identity provider configured in step
143143
### To configure direct federation in the Azure AD portal
144144

145145
1. Go to the [Azure portal](https://portal.azure.com/). In the left pane, select **Azure Active Directory**.
146-
2. Select **Organizational Relationships**.
147-
3. Select **Identity providers**, and then select **New SAML/WS-Fed IdP**.
146+
2. Select **Organizational Relationships** > **All identity providers** (or **External Identities** > **All identity providers**).
147+
3. Select , and then select **New SAML/WS-Fed IdP**.
148148

149149
![Screenshot showing button for adding a new SAML or WS-Fed IdP](media/direct-federation/new-saml-wsfed-idp.png)
150150

@@ -191,8 +191,8 @@ Now test your direct federation setup by inviting a new B2B guest user. For deta
191191
## How do I edit a direct federation relationship?
192192

193193
1. Go to the [Azure portal](https://portal.azure.com/). In the left pane, select **Azure Active Directory**.
194-
2. Select **Organizational Relationships**.
195-
3. Select **Identity providers**
194+
2. Select **Organizational Relationships** (or **External Identities**).
195+
3. Select **All identity providers**
196196
4. Under **SAML/WS-Fed identity providers**, select the provider.
197197
5. In the identity provider details pane, update the values.
198198
6. Select **Save**.
@@ -203,8 +203,8 @@ You can remove your direct federation setup. If you do, direct federation guest
203203
To remove direct federation with an identity provider in the Azure AD portal:
204204

205205
1. Go to the [Azure portal](https://portal.azure.com/). In the left pane, select **Azure Active Directory**.
206-
2. Select **Organizational Relationships**.
207-
3. Select **Identity providers**.
206+
2. Select **Organizational Relationships** (or **External Identities**).
207+
3. Select **All identity providers**.
208208
4. Select the identity provider, and then select **Delete**.
209209
5. Select **Yes** to confirm deletion.
210210

articles/active-directory/b2b/google-federation.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ services: active-directory
77
ms.service: active-directory
88
ms.subservice: B2B
99
ms.topic: conceptual
10-
ms.date: 03/05/2020
10+
ms.date: 05/11/2020
1111

1212
ms.author: mimart
1313
author: msmimart
@@ -88,8 +88,8 @@ Now you'll set the Google client ID and client secret, either by entering it in
8888

8989
#### To configure Google federation in the Azure AD portal
9090
1. Go to the [Azure portal](https://portal.azure.com). In the left pane, select **Azure Active Directory**.
91-
2. Select **Organizational Relationships**.
92-
3. Select **Identity providers**, and then click the **Google** button.
91+
2. Select **Organizational Relationships** (or **External Identities**).
92+
3. Select **All identity providers**, and then click the **Google** button.
9393
4. Enter a name. Then enter the client ID and client secret you obtained earlier. Select **Save**.
9494

9595
![Screenshot showing the Add Google identity provider page](media/google-federation/google-identity-provider.png)
@@ -111,8 +111,8 @@ You can delete your Google federation setup. If you do so, Google guest users wh
111111

112112
### To delete Google federation in the Azure AD portal:
113113
1. Go to the [Azure portal](https://portal.azure.com). In the left pane, select **Azure Active Directory**.
114-
2. Select **Organizational Relationships**.
115-
3. Select **Identity providers**.
114+
2. Select **Organizational Relationships** (or **External Identities**).
115+
3. Select **All identity providers**.
116116
4. On the **Google** line, select the context menu (**...**) and then select **Delete**.
117117

118118
![Screenshot showing the Delete option for the social identity provider](media/google-federation/google-social-identity-providers.png)

articles/active-directory/b2b/one-time-passcode.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ services: active-directory
77
ms.service: active-directory
88
ms.subservice: B2B
99
ms.topic: conceptual
10-
ms.date: 04/08/2019
10+
ms.date: 05/11/2020
1111

1212
ms.author: mimart
1313
author: msmimart
@@ -54,7 +54,7 @@ When a guest user redeems an invitation or uses a link to a resource that has be
5454

5555
At the time of invitation, there's no indication that the user you're inviting will use one-time passcode authentication. But when the guest user signs in, one-time passcode authentication will be the fallback method if no other authentication methods can be used.
5656

57-
You can view guest users who authenticate with one-time passcodes in the Azure portal by going to **Azure Active Directory** > **Organizational relationships** > **Users from other organizations**.
57+
You can view guest users who authenticate with one-time passcodes in the Azure portal by going to **Azure Active Directory** > **Users**.
5858

5959
![Screenshot showing a one-time passcode user with Source value of OTP](media/one-time-passcode/otp-users.png)
6060

@@ -70,8 +70,7 @@ It might take a few minutes for the opt-in action to take effect. After that, on
7070
### To opt in using the Azure AD portal
7171
1. Sign in to the [Azure portal](https://portal.azure.com/) as an Azure AD global administrator.
7272
2. In the navigation pane, select **Azure Active Directory**.
73-
3. Under **Manage**, select **Organizational Relationships**.
74-
4. Select **Settings**.
73+
3. Select **Organizational Relationships** > **Settings** (or select **External Identities** > **External collaboration settings**).
7574
5. Under **Enable Email One-Time Passcode for guests (Preview)**, select **Yes**.
7675

7776
### To opt in using PowerShell
@@ -137,8 +136,7 @@ It may take a few minutes for the opt-out action to take effect. If you turn off
137136
### To turn off the preview using the Azure AD portal
138137
1. Sign in to the [Azure portal](https://portal.azure.com/) as an Azure AD global administrator.
139138
2. In the navigation pane, select **Azure Active Directory**.
140-
3. Under **Manage**, select **Organizational Relationships**.
141-
4. Select **Settings**.
139+
3. Select **Organizational Relationships** > **Settings** (or select **External Identities** > **External collaboration settings**).
142140
5. Under **Enable Email One-Time Passcode for guests (Preview)**, select **No**.
143141

144142
### To turn off the preview using PowerShell

articles/active-directory/b2b/redemption-experience.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ services: active-directory
77
ms.service: active-directory
88
ms.subservice: B2B
99
ms.topic: conceptual
10-
ms.date: 03/19/2020
10+
ms.date: 05/11/2020
1111

1212
ms.author: mimart
1313
author: msmimart
@@ -98,7 +98,7 @@ When a guest signs in to access resources in a partner organization for the firs
9898

9999
![Screenshot showing new terms of use](media/redemption-experience/terms-of-use-accept.png)
100100

101-
You can configure see [terms of use](../governance/active-directory-tou.md) in **Manage** > **Organizational relationships** > **Terms of use**.
101+
You can configure [terms of use](../governance/active-directory-tou.md) in **Organizational relationships** (or **External Identities**) > **Terms of use**.
102102

103103
3. Unless otherwise specified, the guest is redirected to the Apps access panel, which lists the applications the guest can access.
104104

articles/active-directory/conditional-access/faqs.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,7 @@ manager: daveba
1414
ms.reviewer: calebb
1515

1616
ms.collection: M365-identity-device-management
17+
ms.custom: has-adal-ref
1718
---
1819
# Azure Active Directory Conditional Access FAQs
1920

0 commit comments

Comments
 (0)