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
The browser caches the certificate after the certificate picker appears. If the user retries, the cached certificate is used automatically. The user should close the browser, and reopen a new session to try CBA again.
121
121
122
122
- question: |
123
-
Why does not proof up for registering other auth methods come up when I use single factor certificates?
123
+
Why doesn't proof up for registering other auth methods come up when I use single factor certificates?
124
124
answer: |
125
-
A user will be considered MFA capable when a user is in scope for Certificate-based authentication auth method. This means user will not be able to use proof up as part of their authentication to registerd other available methods and should have MFA via another method to register other available auth methods.
125
+
A user is considered capable for MFA when the user is in scope for **Certificate-based authentication** in the Authentication methods policy. This policy requirement means a user can't use proof up as part of their authentication to register other available methods.
126
126
127
127
- question: |
128
128
How can I use single-factor certificates to complete MFA?
129
129
answer: |
130
-
We have support for single factor CBA to get MFA. CBA SF + PSI (passwordless phone sign in) and CBA SF + FIDO2 are the two supported combinations to get MFA using single factor certificates.
130
+
We have support for single factor CBA to get MFA. CBA SF + passwordless phone sign-in (PSI) and CBA SF + FIDO2 are the two supported combinations to get MFA using single factor certificates.
131
131
[MFA with single factor certificates](../authentication/concept-certificate-based-authentication-technical-deep-dive.md#mfa-authentication-flow-using-single-factor-certificates-and-passwordless-sign-in)
132
132
133
133
- question: |
@@ -146,7 +146,16 @@ sections:
146
146
GET https://graph.microsoft.com/v1.0/users?$filter=certificateUserIds/any(x:x eq '[email protected]')
147
147
```
148
148
149
-
149
+
- question: |
150
+
After a CRL endpoint is configured, end users aren't able to sign in and they see the following diagnostic message:
151
+
152
+
```http
153
+
AADSTS500173: Unable to download CRL. Invalid status code Forbidden from CRL distribution point
154
+
errorCode: 500173
155
+
```
156
+
157
+
answer: |
158
+
This is commonly seen when a firewall rule setting blocks access to the CRL endpoint.
Copy file name to clipboardExpand all lines: articles/azure-percept/includes/retire.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,15 +2,15 @@
2
2
author: yvonne-dq
3
3
ms.service: azure-percept
4
4
ms.topic: include
5
-
ms.date: 02/08/2023
5
+
ms.date: 02/22/2023
6
6
ms.author: amiyouss
7
7
ROBOTS: NOINDEX
8
8
---
9
9
10
10
> [!IMPORTANT]
11
11
> **Retirement of Azure Percept DK:**
12
12
>
13
-
>**Update February 22, 2023**: A firmware update that enables the Vision SoM and Audio SOM to retain their functionality with the DK beyond the retirement date, is now available [here](https://aka.ms/audio_vision_som_update).
13
+
>**Update February 22, 2023**: A firmware update for the Percept DK Vision and Audio accessory components (also known as Vision and Audio SOM) is now available [here](https://aka.ms/audio_vision_som_update), and will enable the accessory components to continue functioning beyond the retirement date.
14
14
>
15
15
>The Azure Percept preview including the Percept DK, Audio Accessory, and associated supporting Azure services will be retired March 30th, 2023.
Copy file name to clipboardExpand all lines: articles/azure-percept/index.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
### YamlMime:Landing
2
2
title: Azure Percept documentation
3
-
summary: Update February 22, 2023 A firmware update that enables the Vision SoM and Audio SOM to retain their functionality with the DK beyond the retirement date, is now available. The Azure Percept preview including the Percept DK, Audio Accessory, and associated supporting Azure services will be retired March 30th, 2023. Please see the Retirement of Azure Percept DK article for information on the firmware update and about how these changes will affect you. # < 600 chars
3
+
summary: Update 22 February 2023 - A firmware update for the Percept DK Vision and Audio accessory components (also known as Vision and Audio SOM) is now available [here](https://aka.ms/audio_vision_som_update), and will enable the accessory components to continue functioning beyond the retirement date. # < 300 chars
Copy file name to clipboardExpand all lines: articles/azure-percept/retirement-of-azure-percept-dk.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,13 +5,13 @@ author: yvonne-dq
5
5
ms.author: amiyouss
6
6
ms.service: azure-percept
7
7
ms.topic: overview
8
-
ms.date: 02/08/2023
8
+
ms.date: 02/22/2023
9
9
ROBOTS: NOINDEX
10
10
---
11
11
12
12
# Retirement of Azure Percept DK
13
13
14
-
**Update February 22, 2023**: A firmware update that enables the Vision SoM and Audio SOM to retain their functionality with the DK beyond the retirement date, is now available [here](https://aka.ms/audio_vision_som_update).
14
+
**Update February 22, 2023**: A firmware update for the Percept DK Vision and Audio accessory components (also known as Vision and Audio SOM) is now available [here](https://aka.ms/audio_vision_som_update), and will enable the accessory components to continue functioning beyond the retirement date.
15
15
16
16
The Azure Percept preview including the Percept DK, Audio Accessory, and associated supporting Azure services will be retired March 30th, 2023.
0 commit comments