Skip to content

Commit e6bb682

Browse files
authored
Clarify troubleshooting steps for Conditional Access issues
1 parent 75ee36a commit e6bb682

File tree

1 file changed

+13
-13
lines changed

1 file changed

+13
-13
lines changed

Teams/teams-rooms-and-devices/teams-android-devices-conditional-access-issues.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -50,15 +50,15 @@ These issues can occur for the following reasons:
5050

5151
## Resolution
5252

53-
When troubleshooting Conditional Access issues, start by checking the affected user’s sign-in details and validating whether the device meets policy requirements. These checks can be performed either through automated tools or manually, as outlined earlier in this article.
53+
When you troubleshoot Conditional Access issues, start by checking the affected user’s sign-in details. Verify that the device meets policy requirements. These checks can be performed either through automated tools or manually, as outlined in the following sections.
5454

55-
As Microsoft Teams Android devices transition to **Intune AOSP device management**, administrators can take advantage of device attributessuch as **`device.displayName`**in Conditional Access filters. This allows policies to be targeted more precisely, based on how devices are named.
55+
As Microsoft Teams Android devices transition to **Intune AOSP device management**, administrators can take advantage of device attributes (such as `device.displayName`) in Conditional Access filters. This practice enables policies to be targeted more precisely, based on how devices are named.
5656

57-
The `device.displayName` attribute is especially useful because it includes the device manufacturer information early in the sign-in process, even before Intune completes full enrollment. Once the device finishes enrollment, Intune also reports additional properties such as updated display name, make, model, and compliance status to Microsoft Entra. Because this reporting can take time, using `displayName` in your filter rules helps ensure that devices are properly matched from the start.
57+
The `device.displayName` attribute is especially useful because it includes the device manufacturer information early in the sign-in process, even before Intune completes full enrollment. After the device finishes enrollment, Intune also reports additional properties (such as updated display name, make, model, and compliance status) to Microsoft Entra. Because this reporting can take time, using `displayName` in your filter rules helps make sure that devices are correctly matched at the start of the process.
5858

5959
### Automated checks
6060

61-
The automated option is to run the [Microsoft Teams Rooms Sign in](https://testconnectivity.microsoft.com/tests/TeamsMTRDeviceSignIn/input) connectivity test in the Microsoft Remote Connectivity Analyzer tool. This tool is used to troubleshoot connectivity issues that affect Teams. The connectivity test performs checks to verify a specific user's permissions to sign in to Teams by using a Teams Rooms device.
61+
To use the automatic option, run the [Microsoft Teams Rooms Sign in](https://testconnectivity.microsoft.com/tests/TeamsMTRDeviceSignIn/input) connectivity test in the Microsoft Remote Connectivity Analyzer tool. This tool helps you to troubleshoot connectivity issues that affect Teams. The connectivity test performs checks to verify a specific user's permissions to sign in to Teams by using a Teams Rooms device.
6262

6363
> [!NOTE]
6464
>
@@ -67,14 +67,14 @@ The automated option is to run the [Microsoft Teams Rooms Sign in](https://testc
6767
6868
To run the connectivity test, follow these steps:
6969

70-
1. Open a web browser and navigate to the [Microsoft Teams Rooms Sign in](https://testconnectivity.microsoft.com/tests/TeamsMTRDeviceSignIn/input) connectivity test.
70+
1. In a web browser, navigate to the [Microsoft Teams Rooms Sign in](https://testconnectivity.microsoft.com/tests/TeamsMTRDeviceSignIn/input) connectivity test.
7171
1. Sign in by using the credentials of a Global Administrator account.
7272
1. Specify the username for the account that can't access the Teams Rooms app.
7373
1. In the **Device Selection** field, select a type for the affected user's device.
74-
1. Enter the verification code that's displayed, and then **select Verify**.
74+
1. Enter the verification code that's displayed, and then select **Verify**.
7575
1. Select the checkbox to accept the terms of agreement, and then select **Perform Test**.
7676

77-
After the test finishes, the screen displays details about all the checks that were performed and whether the test succeeded, failed, or was successful but displayed a few warnings. Select the provided link for more information about the warnings and failures, and about how to resolve them.
77+
After the test finishes, the screen displays details about all the checks that were performed and whether the test succeeded, failed, or was successful but displayed a few warnings. For more information about the warnings and failures, and about how to resolve them, select the provided link.
7878

7979
### Manual checks
8080

@@ -87,7 +87,7 @@ To manually check user access to the Teams app, follow these steps:
8787
- **Status**: Select **Failure**, and then select **Apply**.
8888
- **Application**: Enter **Teams**, and then select **Apply**.
8989

90-
:::image type="content" source="media/teams-android-devices-conditional-access-issues/add-filters.png" alt-text="Screenshot of the Status and Application filters.":::
90+
:::image type="content" source="media/teams-android-devices-conditional-access-issues/add-filters.png" alt-text="The Status and Application filters are available options to run a manual check on user access to the Teams app.":::
9191
1. For the affected usernames, look for items that have the following **Application** values:
9292

9393
- Microsoft Teams
@@ -99,15 +99,15 @@ To manually check user access to the Teams app, follow these steps:
9999
- Failure reason
100100
- Additional Details
101101

102-
:::image type="content" source="media/teams-android-devices-conditional-access-issues/sign-in-details-basic-info.png" alt-text="Screenshot of the Basic info page of the sign-in activity details.":::
102+
:::image type="content" source="media/teams-android-devices-conditional-access-issues/sign-in-details-basic-info.png" alt-text="The Basic info page of the sign-in page shows activity details.":::
103103
1. If the sign-in error code seems to be related to compliance, select the **Conditional Access** tab, and then look for policies that show a **Failure** result.
104104

105-
:::image type="content" source="media/teams-android-devices-conditional-access-issues/sign-in-details-conditional-access.png" alt-text="Screenshot of the Conditional Access page of the sign-in activity details.":::
105+
:::image type="content" source="media/teams-android-devices-conditional-access-issues/sign-in-details-conditional-access.png" alt-text="The Conditional Access page of the sign-in activity details shows policy compliance results.":::
106106
1. Review the policy details.
107107

108-
:::image type="content" source="media/teams-android-devices-conditional-access-issues/conditional-access-policy-details.png" alt-text="Screenshot of the Conditional Access policy details.":::
108+
:::image type="content" source="media/teams-android-devices-conditional-access-issues/conditional-access-policy-details.png" alt-text="The Conditional Access policy details page shows compliance failure details per policy.":::
109109

110-
After you identify the specific Conditional Access policy that's causing the issue, you can use [device filters](/azure/active-directory/conditional-access/concept-condition-filters-for-devices) to exclude the affected device from the policy. Commonly used device properties in device filters are *manufacturer* and *model*. These are used together with the *Contains*, *StartsWith*, and *In* operators.
110+
After you identify the specific Conditional Access policy that's causing the issue, you can use [device filters](/azure/active-directory/conditional-access/concept-condition-filters-for-devices) to exclude the affected device from the policy. Some of the commonly used device properties in device filters are *manufacturer* and *model*. These are used together with the *Contains*, *StartsWith*, and *In* operators.
111111

112112
> [!NOTE]
113113
>
@@ -117,7 +117,7 @@ After you identify the specific Conditional Access policy that's causing the iss
117117
118118
The following screenshot shows a sample device filter.
119119

120-
:::image type="content" source="media/teams-android-devices-conditional-access-issues/device-filter.png" alt-text="Screenshot of an example device filter.":::
120+
:::image type="content" source="media/teams-android-devices-conditional-access-issues/device-filter.png" alt-text="Example of a device filter for a device object.":::
121121

122122
## References
123123

0 commit comments

Comments
 (0)