Skip to content

Commit b343283

Browse files
committed
Learn Editor: Update teams-android-devices-conditional-access-issues.md
1 parent a1f209e commit b343283

1 file changed

Lines changed: 5 additions & 1 deletion

File tree

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

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,11 @@ These issues can occur for the following reasons:
5050

5151
## Resolution
5252

53-
Identify the specific cause of the issue by checking multiple details about the affected user's access to the Teams app. To perform the checks that are required, you can either use an automated option or run the checks manually by using the steps provided.
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.
54+
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 allows policies to be targeted more precisely, based on how devices are named.
56+
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.
5458

5559
### Automated checks
5660

0 commit comments

Comments
 (0)