Support Request – Microsoft Teams (macOS) Persistent Location Services Prompts Despite Explicit User Denial

Question

Support Contract

Unified / Premier Support

Product

Microsoft Teams (new client for macOS) Bundle Identifier: com.microsoft.teams2

Platform

macOS Ventura / Sonoma (and later) Apple TCC (Transparency, Consent and Control)

---

Business Impact Summary (Executive Overview)

Microsoft Teams for macOS does not respect an explicit user denial of Location Services, as defined by the macOS privacy model. Although macOS correctly enforces the denial, Teams continues to prompt users through repeated application-level notifications, creating a poor user experience and privacy concern.

This behavior impacts user trust and forces organizations to deploy undesirable workarounds (notification suppression, browser-only usage, or MDM coercion).

We are requesting product-level clarification and escalation to the Teams macOS Product Group.

---

Problem Description

When a user sets Location Services → Never for Microsoft Teams in macOS system settings:

macOS correctly blocks access to CoreLocation.

Microsoft Teams detects the denial but:

continues to probe for location access,

  repeatedly generates **internal Teams notifications** prompting the user to enable location services.
```There is **no configuration option inside Microsoft Teams** to permanently disable location services or acknowledge a definitive refusal.

---
## Expected Product Behavior

In alignment with macOS platform guidelines and privacy best practices:

An explicit user choice of **“Never”** should be treated as final.

Teams may optionally present:

   a **single informational message** explaining functional limitations (e.g., emergency calling).
   
   No repeated prompts or notifications should occur after denial.
   
---
## Actual Behavior

Location access is technically blocked (macOS works correctly).

Teams continues to:

   test location access,
   
```sql
  issue repeated notifications from within the application.

  
  Notifications:

  
     are not system dialogs,

     
        persist across restarts and permission resets,

        
           can only be suppressed by disabling **all** Teams notifications system-wide.
```---
## Technical Notes

The issue is **not a macOS bug**.

It appears to be a **design decision within the Teams macOS client**:

   refusal to accept a durable *Denied* state from the OS,
   
```json
  reliance on application-level prompts rather than system consent.

  
  Attempts to reset permissions using `tccutil reset LocationServices com.microsoft.teams2` fail on modern macOS versions due to protected TCC entries, leaving users without remediation options.

  
  Legal requirements (E911/E112) do **not justify persistent user coercion** once consent has been explicitly denied.
```---
## Organizational Impact

In managed and privacy-sensitive environments (education, public sector, research):

Users report reduced trust in Teams.

IT departments are forced to:

   disable Teams notifications entirely,
   
```sql
  mandate browser-only usage of Teams,

  
     or enforce restrictive MDM profiles.
```These are **workarounds**, not solutions, and negatively affect product adoption.

---
## Requested Actions from Microsoft Support

**Confirm whether this behavior is intended** for the Teams macOS client.

**Escalate to the Teams macOS Product Group** for review.

Provide one of the following:

   product roadmap clarification,
   
```yaml
  official mitigation strategy,

  
     or acknowledgment of this as a design defect.

     
     Clarify if Microsoft plans to introduce:

     
        a permanent “Disable location services” setting,

        
           or durable respect of macOS TCC denial signals.
```---
## Conclusion

This ticket does not request a workaround, but a **product-level resolution or clarification**.

Microsoft Teams on macOS currently behaves in a way that is inconsistent with:

macOS privacy conventions,

user consent expectations,

and enterprise privacy standards.

We respectfully request escalation beyond frontline support
# Support Request – Microsoft Teams (macOS)

## Persistent Location Services Prompts Despite Explicit User Denial

### Support Contract

Unified / Premier Support

### Product

Microsoft Teams (new client for macOS)  
Bundle Identifier: `com.microsoft.teams2`

### Platform

macOS Ventura / Sonoma (and later)  
Apple TCC (Transparency, Consent and Control)

---
## Business Impact Summary (Executive Overview)

Microsoft Teams for macOS does **not respect an explicit user denial of Location Services**, as defined by the macOS privacy model.  
Although macOS correctly enforces the denial, Teams continues to prompt users through **repeated application-level notifications**, creating a poor user experience and privacy concern.

This behavior impacts user trust and forces organizations to deploy undesirable workarounds (notification suppression, browser-only usage, or MDM coercion).

We are requesting **product-level clarification and escalation to the Teams macOS Product Group**.

---
## Problem Description

When a user sets **Location Services → Never** for Microsoft Teams in macOS system settings:

macOS correctly blocks access to CoreLocation.

Microsoft Teams detects the denial but:

   continues to probe for location access,
   
```yaml
  repeatedly generates **internal Teams notifications** prompting the user to enable location services.
```There is **no configuration option inside Microsoft Teams** to permanently disable location services or acknowledge a definitive refusal.

---
## Expected Product Behavior

In alignment with macOS platform guidelines and privacy best practices:

An explicit user choice of **“Never”** should be treated as final.

Teams may optionally present:

   a **single informational message** explaining functional limitations (e.g., emergency calling).
   
   No repeated prompts or notifications should occur after denial.
   
---
## Actual Behavior

Location access is technically blocked (macOS works correctly).

Teams continues to:

   test location access,
   
```yaml
  issue repeated notifications from within the application.

  
  Notifications:

  
     are not system dialogs,

     
        persist across restarts and permission resets,

        
           can only be suppressed by disabling **all** Teams notifications system-wide.
```---
## Technical Notes

The issue is **not a macOS bug**.

It appears to be a **design decision within the Teams macOS client**:

   refusal to accept a durable *Denied* state from the OS,
   
```xml
  reliance on application-level prompts rather than system consent.

  
  Attempts to reset permissions using `tccutil reset LocationServices com.microsoft.teams2` fail on modern macOS versions due to protected TCC entries, leaving users without remediation options.

  
  Legal requirements (E911/E112) do **not justify persistent user coercion** once consent has been explicitly denied.
```---
## Organizational Impact

In managed and privacy-sensitive environments (education, public sector, research):

Users report reduced trust in Teams.

IT departments are forced to:

   disable Teams notifications entirely,
   
```sql
  mandate browser-only usage of Teams,

  
     or enforce restrictive MDM profiles.
```These are **workarounds**, not solutions, and negatively affect product adoption.

---
## Requested Actions from Microsoft Support

**Confirm whether this behavior is intended** for the Teams macOS client.

**Escalate to the Teams macOS Product Group** for review.

Provide one of the following:

   product roadmap clarification,
   
```yaml
  official mitigation strategy,

  
     or acknowledgment of this as a design defect.

     
     Clarify if Microsoft plans to introduce:

     
        a permanent “Disable location services” setting,

        
           or durable respect of macOS TCC denial signals.
```---
## Conclusion

This ticket does not request a workaround, but a **product-level resolution or clarification**.

Microsoft Teams on macOS currently behaves in a way that is inconsistent with:

macOS privacy conventions,

user consent expectations,

and enterprise privacy standards.

We respectfully request escalation beyond frontline support

Answer 1

Disclaimer: Since you described your issue in English, I will also provide my response in English, even though the support site you are using is based in fr-fr. If you prefer a French response, please feel free to let me know.
Dear @Denis Soulet,

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.