Teams for Mac screen sharing permission loop on macOS Tahoe 26.4 — TCC permissions verified correct

Terra Strickland 0 Reputation points
2026-04-02T14:29:01.3166667+00:00

We are an IT support and cybersecurity MSP managing Mac devices via Addigy MDM. We have a customer on macOS Tahoe 26.4 (build 25E246) running Microsoft Teams version 26059.604.4471.2584 who is unable to share their screen in Teams meetings.

When the user clicks Share in a meeting, Teams prompts them to open System Settings to enable Screen Recording. However, the permission is already granted and confirmed at every level:

  • PPPC profile deployed via Addigy MDM targeting com.microsoft.teams2 with the correct code requirement (identifier "com.microsoft.teams2" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists / and certificate leaf[field.1.2.840.113635.100.6.1.13] / exists */ and certificate leaf[subject.OU] = UBF8T346G9)
  • System-level TCC database shows com.microsoft.teams2 with auth_value=2 (allowed) and auth_reason=4 (MDM policy) for kTCCServiceScreenCapture
  • User-level TCC database also shows com.microsoft.teams2 with auth_value=2 for kTCCServiceScreenCapture
  • System Settings > Privacy & Security > Screen & System Audio Recording shows Microsoft Teams toggled ON with "This setting has been configured by a profile"
  • macOS 26.4 confirmed fix for the PPPC display bug from 26.2

Troubleshooting steps completed:

  1. Verified PPPC profile payload matches codesign output from installed Teams binary
  2. Removed legacy com.microsoft.teams identifier from PPPC profile (was causing a stale denial in TCC)
  3. Cleared Teams cache (Library/Group Containers/UBF8T346G9.com.microsoft.teams and Library/Containers/com.microsoft.teams2)
  4. Fully reinstalled Teams via MDM
  5. Killed all Teams background processes and relaunched
  6. Enabled "Use macOS content sharing" native screen picker in Teams Settings > General — still prompts for permission
  7. Rebooted device

The Teams client appears to not be reading the granted TCC permission correctly and continues to prompt the user despite the permission being verifiably granted at both the system and user level. This affects the customer's ability to present in meetings.

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Other
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-04-02T14:29:26.0666667+00:00

    On macOS, Teams screen sharing depends entirely on macOS Screen Recording (Screen & System Audio Recording) TCC permissions. When those are already granted but Teams still loops on the “enable Screen Recording” prompt, the supported remediation is to reset the macOS Screen Recording permission for Teams and re‑grant it, or to reconfigure it via System Settings.

    From the available documentation:

    1. Screen Recording must be enabled for Microsoft Teams under:
      • macOS Monterey: System Preferences → Security & Privacy → Privacy → Screen Recording
      • macOS Ventura/Sonoma and later: System Settings → Privacy & Security → Screen Recording
    2. If the user did not allow screen sharing the first time, or if permissions are mis‑registered, Teams will continue to prompt until the permission is correctly set and recognized. The documented fix is to:
      • Quit Teams completely.
      • Go to the Screen Recording section in Privacy & Security.
      • Ensure Microsoft Teams is present and enabled.
      • If necessary, remove and re‑add Teams (for Monterey this is done via the “+” button; for Ventura/Sonoma and later, via the toggle after reinstalling Teams).
      • Restart Teams and rejoin the meeting; the user may need to drop from the meeting once when first granting permission.
    3. For the new Teams for Mac client (com.microsoft.teams2), Microsoft explicitly notes that users can:
      • Turn on screen sharing “using the regular in‑app flow when they first try to screen share.”
      • Or “turn on permissions for screen recording under system settings” as an alternative.
    4. There is also an optional “Use macOS content sharing” mode in Teams → Settings → General → Screen sharing. When enabled, Teams uses the native macOS sharing UI. In this mode, giving/taking control is not supported, but the same Screen Recording permission is still required and must be granted at the OS level.

    Given the documented behavior, the supported path is:

    1. Confirm that Screen Recording is enabled for Microsoft Teams in System Settings → Privacy & Security → Screen Recording.
    2. If the loop persists, fully quit Teams, remove and re‑add or re‑toggle the Teams entry in Screen Recording, then restart Teams and re‑attempt sharing so macOS can re‑prompt and re‑bind the permission.
    3. Optionally enable “Use macOS content sharing” in Teams Settings → General → Screen sharing to use the native macOS picker, understanding that remote control is not available in that mode.

    If the issue continues after a clean permission reset and reinstall, it falls outside the documented remediation steps and requires escalation to Microsoft support with client logs from ~/Library/Application Support/Microsoft/Teams/media-stack/ for further investigation.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Anonymous
    2026-04-02T15:40:10.78+00:00

    Hi @Terra Strickland, 

    Good day, I hope you are doing well. 

    I appreciate your time to clarify the issue in detail and the troubleshooting steps you have tried. While I would love to resolve this directly, my current scope and resource limitations do not allow access to the internal systems needed for this type of troubleshooting. In this situation, I would recommend creating a support ticket to Microsoft since you have attempted to perform the initial troubleshooting steps.  

    Once the ticket is created, a technical support engineer will be able to initiate a secure remote session, review backend configurations, run diagnostics, and escalate the case to specialized engineering teams if necessary. These teams are equipped to perform advanced troubleshooting and provide targeted solutions. 

    As moderators, our role is to offer guidance and general troubleshooting steps. Although we do not have access to administrative tools required for backend fixes, we truly appreciate your understanding of these limitations. We hope the information provided helps point you in the right direction, and we are always here to assist as much as possible within our scope. 

    For instructions on submitting a support request, please refer to: Get support - Microsoft 365 admin | Microsoft Learn. 

    I hope you found the answer helpful, and I would greatly appreciate it if you could mark it as accepted. This helps highlight the solution for others who may be searching for similar information in the community. Your contribution not only supports fellow users in finding the right guidance more quickly, but also helps build a more resourceful and collaborative space for everyone. 

    Thank you for your kindness and contributions to the forum.   

    If you have extra questions about this answer, please click "Comment". 

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.     

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.