Skip to content

Commit a2ae233

Browse files
authored
Merge pull request #48876 from MicrosoftDocs/master
8/13 AM Publish
2 parents 17fe5fe + b514381 commit a2ae233

File tree

136 files changed

+1650
-1230
lines changed

Some content is hidden

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

136 files changed

+1650
-1230
lines changed

.openpublishing.redirection.json

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27083,6 +27083,10 @@
2708327083
"source_path": "articles/active-directory/device-management-azuread-joined-devices-frx.md",
2708427084
"redirect_url": "/azure/active-directory/devices/azuread-joined-devices-frx",
2708527085
"redirect_document_id": true
27086+
},
27087+
{
27088+
"source_path": "articles/cognitive-services/Bing-Image-Search/sdk.md",
27089+
"redirect_url": "/azure/cognitive-services/Bing-Image-Search/image-search-sdk-quickstart"
2708627090
},
2708727091
{
2708827092
"source_path": "articles/active-directory/active-directory-conditional-access-baseline-protection.md",

articles/active-directory/b2b/add-users-information-worker.md

Lines changed: 84 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,38 +1,110 @@
11
---
22

33
title: Add B2B collaboration users as an information worker - Azure Active Directory | Microsoft Docs
4-
description: B2B collaboration allows information workers to add users from their organization to Azure AD for access | Microsoft Docs
4+
description: B2B collaboration allows information workers and app owners to add guest users to Azure AD for access | Microsoft Docs
55

66
services: active-directory
77
ms.service: active-directory
88
ms.component: B2B
99
ms.topic: article
10-
ms.date: 05/11/2018
10+
ms.date: 08/08/2018
1111

1212
ms.author: mimart
1313
author: msmimart
1414
manager: mtillman
15-
ms.reviewer: sasubram
15+
ms.reviewer: mal
1616

1717
---
1818

19-
# How do information workers add B2B collaboration users to Azure Active Directory?
19+
# How users in your organization can invite guest users to an app
2020

21-
Information workers can use the [Application Access Panel](http://myapps.microsoft.com) to add B2B collaboration users to groups and applications that they administer.
21+
After a guest user has been added to the directory in Azure AD, an application owner can send the guest user a direct link to the app they want to share. Azure AD admins can also set up self-service management so that application owners can manage their own guest users, even if the guest users haven’t been added to the directory yet. When an app is configured for self-service, the application owner uses their Access Panel to invite a guest user to an app or add a guest user to a group that has access to the app. Self-service app management requires some initial setup by an admin. The following is a summary of the setup steps (for more detailed instructions, see [Prerequisites](#prerequisites) later on this page):
2222

23-
After a guest user is added to the directory, the information worker can either send the guest user a direct link to a shared app, or the guest user can click the redemption URL in the invitation email. For more information about the redemption process, see [B2B collaboration invitation redemption](redemption-experience.md).
23+
- Enable self-service group management for your tenant
24+
- Create a group to assign to the app and make the user an owner
25+
- Configure the app for self-service and assign the group to the app
2426

25-
## Information workers adding B2B collaboration users to an application
26-
Assign B2B collaboration users to an app as an information worker in a partner organization, as shown in the following video:
27+
## Invite a guest user to an app from the Access Panel
2728

28-
>[!VIDEO https://channel9.msdn.com/Blogs/Azure/information-worker-assign-to-apps/Player]
29+
After an app is configured for self-service, application owners can use their own Access Panel to invite a guest user to the app they want to share. The guest user doesn't necessarily need to be added to Azure AD in advance.
2930

30-
## Information workers adding B2B collaboration users to a group
31+
1. Open your Access Panel by going to `https://myapps.microsoft.com`.
32+
2. Point to the app, select the ellipses (**...**), and then select **Manage app**.
33+
34+
![Access Panels manage app](media/add-users-iw/access-panel-manage-app.png)
35+
36+
3. At the top of the users list, select **+**.
37+
38+
![Access Panel add a user](media/add-users-iw/access-panel-manage-app-add-user.png)
39+
40+
4. In the **Add members** search box, type the email address for the guest user. Optionally, include a welcome message.
41+
42+
![Access Panel invitation](media/add-users-iw/access-panel-invitation.png)
43+
44+
5. Select **Add** to send an invitation to the guest user. After you send the invitation, the user account is automatically added to the directory as a guest.
45+
46+
## Invite someone to join a group that has access to the app
47+
After an app is configured for self-service, application owners can invite guest users to the groups they manage that have access to the apps they want to share. The guest users don't have to already exist in the directory. The application owner follows these steps to invite a guest user to the group so that they can access the app.
48+
49+
1. Make sure you're an owner of the self-service group that has access to the app you want to share.
50+
2. Open your Access Panel by going to `https://myapps.microsoft.com`.
51+
3. Select the **Groups** app.
52+
53+
![Access Panel groups app](media/add-users-iw/access-panel-groups.png)
54+
55+
4. Under **Groups I own**, select the group that has access to the app you want to share.
56+
57+
![Access Panel groups I own](media/add-users-iw/access-panel-groups-i-own.png)
58+
59+
5. At the top of the group members list, select **+**.
60+
61+
![Access Panel groups add a member](media/add-users-iw/access-panel-groups-add-member.png)
62+
63+
6. In the **Add members** search box, type the email address for the guest user. Optionally, include a welcome message.
64+
65+
![Access Panel group invitation](media/add-users-iw/access-panel-invitation.png)
66+
67+
7. Select **Add** to automatically send the invitation to the guest user. After you send the invitation, the user account is automatically added to the directory as a guest.
68+
69+
70+
## Prerequisites
71+
72+
Self-service app management requires some initial setup by a Global Administrator and an Azure AD administrator. As part of this setup, you'll configure the app for self-service and assign a group to the app that the application owner can manage. You can also configure the group to allow anyone to request membership but require a group owner's approval. (Learn more about [self-service group management](https://docs.microsoft.com/azure/active-directory/users-groups-roles/groups-self-service-management).)
3173

32-
Information workers can similarly add B2B collaboration users to an assigned group that is enabled for self-service group management.
3374
> [!NOTE]
34-
> You cannot add B2B collaboration users to a dynamic group or to a group that is synced with on-premises Active Directory.
75+
> You cannot add guest users to a dynamic group or to a group that is synced with on-premises Active Directory.
76+
77+
### Enable self-service group management for your tenant
78+
1. Sign in to the [Azure portal](https://portal.azure.com) as a Global Administrator.
79+
2. In the navigation panel, select **Azure Active Directory**.
80+
3. Select **Groups**.
81+
4. Under **Settings**, select **General**.
82+
5. Under **Self Service Group Management**, next to **Owners can manage group membership requests in the Access Panel**, select **Yes**.
83+
6. Select **Save**.
84+
85+
### Create a group to assign to the app and make the user an owner
86+
1. Sign in to the [Azure portal](https://portal.azure.com) as an Azure AD administrator or Global Administrator.
87+
2. In the navigation panel, select **Azure Active Directory**.
88+
3. Select **Groups**.
89+
4. Select **New group**.
90+
5. Under **Group type**, select **Security**.
91+
6. Type a **Group name** and **Group description**.
92+
7. Under **Membership type**, select **Assigned**.
93+
8. Select **Create**, and close the **Group** page.
94+
9. On the **Groups - All groups** page, open the group.
95+
10. Under **Manage**, select **Owners** > **Add owners**. Search for the user who should manage access to the application. Select the user, and then click **Select**.
3596

97+
### Configure the app for self-service and assign the group to the app
98+
1. Sign in to the [Azure portal](https://portal.azure.com) as an Azure AD administrator or Global Administrator.
99+
2. In the navigation pane, select **Azure Active Directory**.
100+
3. Under **Manage**, select **Enterprise applications** > **All applications**.
101+
4. In the application list, find and open the app.
102+
5. Under **Manage**, select **Single sign-on**, and configure the application for single sign-on. (For details, see [how to manage single sign-on for enterprise apps](https://docs.microsoft.com/azure/active-directory/manage-apps/configure-single-sign-on-portal).)
103+
6. Under **Manage**, select **Self-service**, and set up self-service app access. (For details, see [how to use self-service app access](https://docs.microsoft.com/azure/active-directory/application-access-panel-self-service-applications-how-to).)
104+
> [!NOTE]
105+
> For the setting **To which group should assigned users be added?** select the group you created in the previous section.
106+
7. Under **Manage**, select **Users and groups**, and verify that the self-service group you created appears in the list.
107+
8. To add the app to the group owner's Access Panel, select **Add user** > **Users and groups**. Search for the group owner and select the user, click **Select**, and then click **Assign** to add the user to the app.
36108

37109
## Next steps
38110

13.1 KB
Loading
12 KB
Loading
110 KB
Loading
38.3 KB
Loading
60.1 KB
Loading
53 KB
Loading

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@ The device state condition excludes hybrid Azure AD joined devices and devices m
116116

117117
![Configure device state](./media/conditions/112.png)
118118

119-
If you want to block access for unmanaged devices, implement [device-based conditional access](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-mam#app-based-or-compliant-device-policy-for-exchange-online-and-sharepoint-online).
119+
If you want to block access for unmanaged devices, implement [device-based conditional access](https://docs.microsoft.com/azure/active-directory/conditional-access/app-based-conditional-access#app-based-or-compliant-device-policy-for-exchange-online-and-sharepoint-online).
120120

121121

122122
## Locations
@@ -150,7 +150,7 @@ For a list of the client apps you can use in your conditional access policy, see
150150

151151
Common use cases for this condition are policies with the following protections:
152152

153-
- Require a [compliant device](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-mam#app-based-or-compliant-device-policy-for-exchange-online-and-sharepoint-online) for mobile and desktop applications that download large amounts of data to the device. At the same time, allow browser access from any device.
153+
- Require a [compliant device](https://docs.microsoft.com/azure/active-directory/conditional-access/app-based-conditional-access#app-based-or-compliant-device-policy-for-exchange-online-and-sharepoint-online) for mobile and desktop applications that download large amounts of data to the device. At the same time, allow browser access from any device.
154154

155155
- Block access from web applications but allow access from mobile and desktop applications.
156156

@@ -174,7 +174,7 @@ Applying this condition only to supported platforms is equal to all device platf
174174

175175
- [Set up SharePoint Online and Exchange Online for Azure Active Directory conditional access](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-no-modern-authentication).
176176

177-
- [Azure Active Directory app-based conditional access](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-mam).
177+
- [Azure Active Directory app-based conditional access](https://docs.microsoft.com/azure/active-directory/conditional-access/app-based-conditional-access).
178178

179179

180180
### Legacy authentication

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

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -791,7 +791,7 @@ Read more about this in our [blog post](https://cloudblogs.microsoft.com/enterpr
791791

792792
For more information, see:
793793

794-
- [Setup application-based conditional access](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-mam)
794+
- [Setup application-based conditional access](https://docs.microsoft.com/azure/active-directory/conditional-access/app-based-conditional-access)
795795

796796
- [Configure managed browser policies](https://aka.ms/managedbrowser)
797797

@@ -1151,7 +1151,7 @@ The following applications will be added by the end of February:
11511151
For more information, see:
11521152

11531153
- [Approved client app requirement](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-technical-reference#approved-client-app-requirement)
1154-
- [Azure AD app-based conditional access](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-mam)
1154+
- [Azure AD app-based conditional access](https://docs.microsoft.com/azure/active-directory/conditional-access/app-based-conditional-access)
11551155

11561156
---
11571157

@@ -1450,7 +1450,7 @@ The following apps are on the list of [approved client apps](https://docs.micros
14501450
For more information, see:
14511451

14521452
- [Approved client app requirement](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-technical-reference#approved-client-app-requirement)
1453-
- [Azure AD app-based conditional access](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-mam)
1453+
- [Azure AD app-based conditional access](https://docs.microsoft.com/azure/active-directory/conditional-access/app-based-conditional-access)
14541454

14551455
---
14561456

@@ -1488,9 +1488,9 @@ For more information, see [on-premises integration](https://docs.microsoft.com/a
14881488
**Service category:** Azure AD
14891489
**Product capability:** Identity security and protection
14901490

1491-
You now can restrict access to Office 365 and other Azure AD-connected cloud apps to [approved client apps](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-technical-reference#approved-client-app-requirement) that support Intune app protection policies by using [Azure AD app-based conditional access](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-mam). Intune app protection policies are used to configure and protect company data on these client applications.
1491+
You now can restrict access to Office 365 and other Azure AD-connected cloud apps to [approved client apps](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-technical-reference#approved-client-app-requirement) that support Intune app protection policies by using [Azure AD app-based conditional access](https://docs.microsoft.com/azure/active-directory/conditional-access/app-based-conditional-access). Intune app protection policies are used to configure and protect company data on these client applications.
14921492

1493-
By combining [app-based](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-mam) with [device-based](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-policy-connected-applications) conditional access policies, you have the flexibility to protect data for personal and company devices.
1493+
By combining [app-based](https://docs.microsoft.com/azure/active-directory/conditional-access/app-based-conditional-access) with [device-based](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-policy-connected-applications) conditional access policies, you have the flexibility to protect data for personal and company devices.
14941494

14951495
The following conditions and controls are now available for use with app-based conditional access:
14961496

@@ -1507,7 +1507,7 @@ The following conditions and controls are now available for use with app-based c
15071507

15081508
- Require approved client app
15091509

1510-
For more information, see [Azure AD app-based conditional access](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-mam).
1510+
For more information, see [Azure AD app-based conditional access](https://docs.microsoft.com/azure/active-directory/conditional-access/app-based-conditional-access).
15111511

15121512
---
15131513

@@ -1604,7 +1604,7 @@ The following apps were added to the list of [approved client apps](https://docs
16041604
For more information, see:
16051605

16061606
- [Approved client app requirement](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-technical-reference#approved-client-app-requirement)
1607-
- [Azure AD app-based conditional access](https://docs.microsoft.com/azure/active-directory/active-directory-conditional-access-mam)
1607+
- [Azure AD app-based conditional access](https://docs.microsoft.com/azure/active-directory/conditional-access/app-based-conditional-access)
16081608

16091609

16101610
---

0 commit comments

Comments
 (0)