Blog Post

Microsoft Teams Blog
2 MIN READ

Policy changes for Microsoft Teams devices using device code flow authentication

dimehta's avatar
dimehta
Icon for Microsoft rankMicrosoft
Apr 01, 2025

First announced in February, Microsoft is rolling out a new Microsoft-managed policy to help further secure your tenants against potential threats to accounts using device code flow (DCF) authentication.

Rollout began in February and will continue until May. The policies will initially be created in report-only mode, allowing admins to review their impact before they’re enforced. You’ll have at least 45 days to evaluate and configure the policies before they’re automatically moved to the "On" state. We recommend taking action as soon as possible to create exclusion lists if you are using Android devices in shared spaces.

To ensure that admins are able to use the remote sign-in and management capabilities of DCF, global admins can create exclusion lists to exclude accounts that sign in on Android-based shared Teams devices. If exclusions aren't set, after sign-out, devices cannot re-authenticate with DCF, which means admins will lose their ability to remotely sign in and manage devices. The screenshot below is an example of how to view the policy for your tenant in the Microsoft Entra admin center.

Policy details for the tenant in the Microsoft Entra admin center

The exclusion lists for this policy should be created by tenants that have deployed Android-based Teams devices in shared spaces like:

  • Microsoft Teams Rooms on Android front-of-room displays and consoles
  • IP Phones (licensed as Teams Shared Devices)
  • Panels
  • Displays

 

Resources:

Updated Apr 01, 2025
Version 1.0

11 Comments

  • Frazze's avatar
    Frazze
    Copper Contributor

    We still don't see this policy in our tenant. Any ideas why we can't see it?
    Is the recommendation to exclude all MTR, Panels and Phones even if the remote login isn't used?

  • paul-lange's avatar
    paul-lange
    Iron Contributor

    The article mentions shared devices. My understanding and short testing today would say that this also affect personal accounts using Teams phones. Correct?

  • AzureGuineaPig's avatar
    AzureGuineaPig
    Copper Contributor

    Is the Microsoft recommendation an excluding user accounts really appropriate in this scenario?  Doesn't that defeat the purpose of the intended protection?  Wouldn't it be a better to create a filter to exclude Teams phones within the organization that would be exempt from this policy, instead of the user accounts which would then still be at risk for the device code flow attacks?

  • SteveUlrichTE's avatar
    SteveUlrichTE
    Brass Contributor

    Can it be assumed that if we do not see this preview policy in our tenant, that we have used device code flow authentication in the last 25 days, and therefore we are using device code flow authentication, and that we do not have to create an exclusion list?

    • dimehta's avatar
      dimehta
      Icon for Microsoft rankMicrosoft

      The delay in seeing the policy could be purely because of your tenant id falling under a later rollout batch. It is advised to create exclusion lists if your tenant has Android based shared teams devices. 

      • Buddit's avatar
        Buddit
        Copper Contributor

        Hi Dimehta,

        Just confirming, we are now in July, I still cannot see the CAP in a few tenant so far. Does this mean that it is still slowly rolling out? 

  • Chris_TenAV's avatar
    Chris_TenAV
    Copper Contributor

    "The exclusion lists for this policy should be created by tenants that have deployed Android-based Teams devices in shared spaces"
    They're not mentioned, but I take it the above also refers to Android-based MTR such as Logi Rallybar, Yealink meetingbar A30 and MeetingBoards used as resources with MTR licenses?