Skip to content

Commit 72305b4

Browse files
authored
Clarify Conditional Access issues for Teams Android devices
1 parent e6bb682 commit 72305b4

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Fix Conditional Access-related issues for Teams Android devices
3-
description: Discusses how to exclude devices from Conditional Access policies or Intune device compliance policies that can prevent users from signing in to or using the Teams app on Android devices.
3+
description: Discusses how to exclude devices from Conditional Access policies or Intune device compliance policies. These policies can prevent users from signing in to or using the Teams app on Android devices.
44
ms.reviewer: taherr
55
ms.topic: troubleshooting
66
ms.date: 05/26/2024
@@ -22,9 +22,9 @@ ms.custom:
2222

2323
## Symptoms
2424

25-
Conditional Access is a Microsoft Entra feature that helps make sure that devices that access corporate resources are correctly managed and secured. If Conditional Access policies are applied to the Microsoft Teams service, Android devices that access Teams must comply with the policies. Such devices include Teams phones, Teams displays, Teams panels, and Teams Rooms on Android. Otherwise, Conditional Access will prevent users from signing in to or using the Teams app on the devices.
25+
Conditional Access is a Microsoft Entra feature that helps make sure that devices that access corporate resources are correctly managed and secured. If Conditional Access policies are applied to the Microsoft Teams service, Android devices that access Teams must comply with the policies. Such devices include Teams phones, Teams displays, Teams panels, and Teams Rooms on Android. Otherwise, Conditional Access prevent users from signing in to or using the Teams app on the devices.
2626

27-
If these policies are applied, you might experience one or more of the following issues on non-compliant devices:
27+
If these policies are applied, you might experience one or more of the following issues on noncompliant devices:
2828

2929
- The devices can't sign in to Teams, or they get stuck in sign-in loops.
3030
- The devices automatically sign out of Teams randomly.
@@ -36,7 +36,7 @@ These issues can occur for the following reasons:
3636

3737
- Unsupported Conditional Access policy or Intune device compliance policy settings
3838

39-
If a device is marked as non-compliant, the Microsoft Entra token-issuing service stops renewing the tokens for the device object or even revokes the token. In this case, the device can't get an updated authentication token, and it's forced to sign out.
39+
If a device is marked as noncompliant, the Microsoft Entra token-issuing service stops renewing the tokens for the device object or even revokes the token. In this case, the device can't get an updated authentication token, and it's forced to sign out.
4040

4141
To check the compliance status of your devices, use the [Intune Device compliance dashboard](/mem/intune/protect/compliance-policy-monitor).
4242

@@ -107,7 +107,7 @@ To manually check user access to the Teams app, follow these steps:
107107

108108
:::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. 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.
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 properties are used together with the *Contains*, *StartsWith*, and *In* operators.
111111

112112
> [!NOTE]
113113
>

0 commit comments

Comments
 (0)