You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/identity-verification-proofing.md
+30-21Lines changed: 30 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,43 +4,52 @@ titleSuffix: Azure AD B2C
4
4
description: Learn about our partners who integrate with Azure AD B2C to provide identity proofing and verification solutions
5
5
services: active-directory-b2c
6
6
author: gargi-sinha
7
-
manager: CelesteDG
7
+
manager: martinco
8
8
ms.reviewer: kengaderdus
9
-
10
9
ms.service: active-directory
11
10
ms.workload: identity
12
11
ms.topic: how-to
13
-
ms.date: 09/13/2022
12
+
ms.date: 01/18/2023
14
13
ms.author: gasinh
15
-
ms.subservice: B2C
16
14
---
17
15
18
16
# Identity verification and proofing partners
19
17
20
-
With Azure AD B2C partners, customers can enable identity verification and proofing of their end users before allowing account registration or access. Identity verification and proofing can check document, knowledge-based information and liveness.
18
+
With Azure Active Directory B2C (Azure AD B2C) and solutions from software-vendor partners, customers can enable end-user identity verification and proofing for account registration. Identity verification and proofing can check documents, knowledge-based information, and liveness.
19
+
20
+
## Architecture diagram
21
+
22
+
The following architecture diagram illustrates the verification and proofing flow.
21
23
22
-
A high-level architecture diagram explains the flow.
24
+

23
25
24
-

26
+
1. User begins registration with a device.
27
+
2. User enters information.
28
+
3. Digital-risk score is assessed, then third-party identity proofing and identity validation occurs.
29
+
4. Identity is validated or rejected.
30
+
5. User attributes are passed to Azure Active Directory B2C.
31
+
6. If user verification is successful, a user account is created in Azure AD B2C during sign-in.
32
+
7. Based on the verification result, the user receives an access-approved or -denied message.
25
33
26
-
Microsoft partners with the following ISV partners.
34
+
## Software vendors and integration documentation
27
35
28
-
| ISV partner | Description and integration walkthroughs |
29
-
|:-------------------------|:--------------|
30
-
||[Deduce](./partner-deduce.md) is an identity verification and proofing provider focused on stopping account takeover and registration fraud. It helps combat identity fraud and creates a trusted user experience. |
31
-
||[eID-Me](./partner-eid-me.md) is an identity verification and decentralized digital identity solution for Canadian citizens. It enables organizations to meet Identity Assurance Level (IAL) 2 and Know Your Customer (KYC) requirements. |
32
-
||[Experian](./partner-experian.md) is an Identity verification and proofing provider that performs risk assessments based on user attributes to prevent fraud. |
33
-
||[IDology](./partner-idology.md) is an Identity verification and proofing provider with ID verification solutions, fraud prevention solutions, compliance solutions, and others.|
34
-
||[Jumio](./partner-jumio.md) is an ID verification service, which enables real-time automated ID verification, safeguarding customer data. |
35
-
||[LexisNexis](./partner-lexisnexis.md) is a profiling and identity validation provider that verifies user identification and provides comprehensive risk assessment based on user’s device. |
36
-
||[Onfido](./partner-onfido.md) is a document ID and facial biometrics verification solution that allows companies to meet *Know Your Customer* and identity requirements in real time. |
36
+
Microsoft partners with independent software vendors (ISVs). Use the following table to locate an ISV and related integration documentation.
37
37
38
-
## Additional information
38
+
| ISV logo | ISV link and description| Integration documentation|
39
+
|---|---|---|
40
+
||[Deduce](https://www.deduce.com/): Identity verification and proofing provider that helps stop account takeover and registration fraud. Use it to combat identity fraud and create a trusted user experience. |[Configure Azure AD B2C with Deduce to combat identity fraud and create a trusted user experience](partner-deduce.md)|
41
+
||[Bluink, Ltd.](https://bluink.ca/): eID-Me is an identity verification and decentralized digital identity solution for Canadian citizens. Use it to meet Identity Assurance Level (IAL) 2 and Know Your Customer (KYC) requirements. |[Configure eID-Me with Azure AD B2C for identity verification](partner-eid-me.md)|
42
+
||[Experian Information Solutions, Inc.](https://www.experian.com/business/products/crosscore): Identity verification and proofing provider with solutions that perform risk assessments based on user attributes. |[Tutorial: Configure Experian with Azure AD B2C](partner-experian.md)|
43
+
||[IDology, a GBG company](https://www.idology.com/solutions/): Identity verification and proofing provider with ID verification, fraud prevention, and compliance solutions.|[Tutorial for configuring IDology with Azure AD B2C](partner-idology.md)|
44
+
||[Jumio](https://www.jumio.com/): Identify verification service with products for real-time, automated ID verification. |[Tutorial for configuring Jumio with Azure AD B2C](partner-jumio.md)|
45
+
||[LexisNexis Risk Solutions Group](https://risk.lexisnexis.com/products/threatmetrix): Profiling and identity validation provider that verifies user identification and provides risk assessment based on user devices. See, ThreatMetrix. |[Tutorial for configuring LexisNexis with Azure AD B2C](partner-lexisnexis.md)|
46
+
||[Onfido](https://onfido.com/): Document ID and facial biometrics verification solutions to meet Know Your Customer (KYC) and identity requirements. |[Tutorial for configuring Onfido with Azure AD B2C](partner-onfido.md)|
39
47
40
-
-[Custom policies in Azure AD B2C](./custom-policy-overview.md)
48
+
## Resources
41
49
42
-
-[Get started with custom policies in Azure AD B2C](./tutorial-create-user-flows.md?pivots=b2c-custom-policy&tabs=applications)
50
+
-[Azure AD B2C custom policy overview](custom-policy-overview.md)
51
+
-[Tutorial: Create user flows and custom policies in Azure Active Directory B2C](tutorial-create-user-flows.md?pivots=b2c-custom-policy&tabs=applications)
43
52
44
53
## Next steps
45
54
46
-
Select a partner in the tables mentioned to learn how to integrate their solution with Azure AD B2C.
55
+
Select and contact a partner from the previous table to get started on solution integration with Azure AD B2C. The partners have similar processes to contact them for a product demo.
Copy file name to clipboardExpand all lines: articles/active-directory/authentication/howto-mfa-nps-extension-errors.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,6 +69,8 @@ Sometimes, your users may get messages from Multi-Factor Authentication because
69
69
|**OathCodeIncorrect**| Wrong code entered\OATH Code Incorrect | The user entered the wrong code. Have them try again by requesting a new code or signing in again. |
70
70
|**SMSAuthFailedMaxAllowedCodeRetryReached**| Maximum allowed code retry reached | The user failed the verification challenge too many times. Depending on your settings, they may need to be unblocked by an admin now. |
71
71
|**SMSAuthFailedWrongCodeEntered**| Wrong code entered/Text Message OTP Incorrect | The user entered the wrong code. Have them try again by requesting a new code or signing in again. |
72
+
|**AuthenticationThrottled**| Too many attempts by user in a short period of time. Throttling. | Microsoft may limit repeated authentication attempts that are performed by the same user in a short period of time. This limitation does not apply to the Microsoft Authenticator or verification code. If you have hit these limits, you can use the Authenticator App, verification code or try to sign in again in a few minutes. |
73
+
|**AuthenticationMethodLimitReached**| Authentication Method Limit Reached. Throttling. | Microsoft may limit repeated authentication attempts that are performed by the same user using the same authentication method type in a short period of time, specifically Voice call or SMS. This limitation does not apply to the Microsoft Authenticator or verification code. If you have hit these limits, you can use the Authenticator App, verification code or try to sign in again in a few minutes.|
Copy file name to clipboardExpand all lines: articles/active-directory/develop/mark-app-as-publisher-verified.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Mark an app as publisher verified
3
-
description: Describes how to mark an app as publisher verified. When an application is marked as publisher verified, it means that the publisher has verified their identity using a Microsoft Partner Network account that has completed the verification process and has associated this MPN account with their application registration.
3
+
description: Describes how to mark an app as publisher verified. When an application is marked as publisher verified, it means that the publisher (application developer) has verified the authenticity of their organization using a Microsoft Partner Network (MPN) account that has completed the verification process and has associated this MPN account with that application registration.
Publisher verification gives app users and organization admins information about the authenticity of a developer who publishes an app that integrates with the Microsoft identity platform.
19
+
Publisher verification gives app users and organization admins information about the authenticity of the developer's organization, who publishes an app that integrates with the Microsoft identity platform.
20
20
21
-
An app that's publisher verified means that the app's publisher has verified their identity with Microsoft. Identity verification includes using a [Microsoft Partner Network (MPN)](https://partner.microsoft.com/membership) account that's been [verified](/partner-center/verification-responses) and associating the MPN account with an app registration.
21
+
An app that's publisher verified means that the app's publisher (app developer) has verified the authenticity of their organization with Microsoft. Verifying an app includes using a Microsoft Partner Network (MPN) account that's been [verified](/partner-center/verification-responses) and associating the MPN account with an app registration.
22
22
23
23
When the publisher of an app has been verified, a blue *verified* badge appears in the Azure Active Directory (Azure AD) consent prompt for the app and on other webpages:
0 commit comments