Skip to content

Commit 86e3743

Browse files
Merge pull request #220204 from csmulligan/csm-exid-code-sampleas-sssu
[EXID] Content freshness update for API invitation and samples
2 parents 23dfd66 + 4c0e5c1 commit 86e3743

File tree

2 files changed

+21
-16
lines changed

2 files changed

+21
-16
lines changed

articles/active-directory/external-identities/code-samples-self-service-sign-up.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,18 +5,18 @@ services: active-directory
55
ms.service: active-directory
66
ms.subservice: B2B
77
ms.topic: sample
8-
ms.date: 06/16/2020
8+
ms.date: 11/30/2022
99

1010
ms.author: mimart
1111
author: msmimart
1212
manager: celestedg
1313
ms.custom: "it-pro"
14-
ms.collection: M365-identity-device-management
14+
ms.collection: engagement-fy23, M365-identity-device-management
1515
---
1616

1717
# Samples for External Identities self-service sign-up
1818

19-
The following tables provide links to code samples for leveraging web APIs in your self-service sign-up user flows using [API connectors](api-connectors-overview.md).
19+
The following tables provide links to code samples for applying web APIs in your self-service sign-up user flows using [API connectors](api-connectors-overview.md).
2020

2121
## API connector Azure Function quickstarts
2222

@@ -40,3 +40,9 @@ The following tables provide links to code samples for leveraging web APIs in yo
4040
| ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
4141
| [IDology](https://github.com/Azure-Samples/active-directory-dotnet-external-identities-idology-identity-verification) | This sample shows how to verify a user identity as part of your self-service sign-up by using an API connector to integrate with IDology. |
4242
| [Experian](https://github.com/Azure-Samples/active-directory-dotnet-external-identities-experian-identity-verification) | This sample shows how to verify a user identity as part of your self-service sign-up by using an API connector to integrate with Experian. |
43+
44+
## Next steps
45+
46+
- [Code and Azure PowerShell samples](code-samples.md)
47+
- [External Identities pricing](external-identities-pricing.md)
48+

articles/active-directory/external-identities/customize-invitation-api.md

Lines changed: 12 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -6,17 +6,18 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: B2B
88
ms.topic: how-to
9-
ms.date: 02/03/2021
9+
ms.date: 12/02/2022
1010

1111
ms.author: mimart
1212
author: msmimart
1313
manager: celestedg
1414

15-
ms.collection: M365-identity-device-management
15+
ms.collection: engagement-fy23, M365-identity-device-management
16+
# Customer intent: As a tenant administrator, I want to customize the invitation process with the API.
1617
---
1718
# Azure Active Directory B2B collaboration API and customization
1819

19-
We've had many customers tell us that they want to customize the invitation process in a way that works best for their organizations. With our API, you can do just that. [https://developer.microsoft.com/graph/docs/api-reference/v1.0/resources/invitation](/graph/api/resources/invitation)
20+
We've had many customers tell us that they want to customize the invitation process. [With our API](/graph/api/resources/invitation), you can customize the invitation process in a way that works best for your organization.
2021

2122
## Capabilities of the invitation API
2223

@@ -25,8 +26,8 @@ The API offers the following capabilities:
2526
1. Invite an external user with *any* email address.
2627

2728
```
28-
"invitedUserDisplayName": "Sam"
29-
"invitedUserEmailAddress": "gsamoogle@gmail.com"
29+
"invitedUserDisplayName": "Taylor"
30+
"invitedUserEmailAddress": "taylor@fabrikam.com"
3031
```
3132
3233
2. Customize where you want your users to land after they accept their invitation.
@@ -35,13 +36,13 @@ The API offers the following capabilities:
3536
"inviteRedirectUrl": "https://myapps.microsoft.com/"
3637
```
3738
38-
3. Choose to send the standard invitation mail through us
39+
3. Choose to send the standard invitation mail through us.
3940
4041
```
4142
"sendInvitationMessage": true
4243
```
4344
44-
with a message to the recipient that you can customize
45+
with a message to the recipient that you can customize.
4546
4647
```
4748
"customizedMessageBody": "Hello Sam, let's collaborate!"
@@ -57,15 +58,15 @@ The API offers the following capabilities:
5758
5859
In this case, you get back a redemption URL from the API that you can embed in an email template, IM, or other distribution method of your choice.
5960
60-
6. Finally, if you are an admin, you can choose to invite the user as member.
61+
6. Finally, if you're an admin, you can choose to invite the user as member.
6162
6263
```
6364
"invitedUserType": "Member"
6465
```
6566
6667
## Determine if a user was already invited to your directory
6768
68-
You can use the invitation API to determine if a user already exists in your resource tenant. This can be useful when you're developing an app that uses the invitation API to invite a user. If the user already exists in your resource directory, they won't receive an invitation, so you can run a query first to determine whether the already email exists as a UPN or other sign-in property.
69+
You can use the invitation API to determine if a user already exists in your resource tenant. This can be useful when you're developing an app that uses the invitation API to invite a user. If the user already exists in your resource directory, they won't receive an invitation, so you can run a query first to determine whether the email already exists as a UPN or other sign-in property.
6970
7071
1. Make sure the user's email domain isn't part of your resource tenant's verified domain.
7172
2. In the resource tenant, use the following get user query where {0} is the email address you're inviting:
@@ -86,8 +87,7 @@ In this mode, whoever is using the API needs to have the permissions to be creat
8687
8788
In app only context, the app needs the User.Invite.All scope for the invitation to succeed.
8889
89-
For more information, refer to: https://developer.microsoft.com/graph/docs/authorization/permission_scopes
90-
90+
For more information, see: https://developer.microsoft.com/graph/docs/authorization/permission_scopes
9191
9292
## PowerShell
9393
@@ -128,6 +128,5 @@ Check out the invitation API reference in [https://developer.microsoft.com/graph
128128
## Next steps
129129

130130
- [What is Azure AD B2B collaboration?](what-is-b2b.md)
131+
- [Add and invite guest users](add-users-administrator.md)
131132
- [The elements of the B2B collaboration invitation email](invitation-email-elements.md)
132-
- [B2B collaboration invitation redemption](redemption-experience.md)
133-
- [Add B2B collaboration users without an invitation](add-user-without-invite.md)

0 commit comments

Comments
 (0)