Uploaded June 2025 | Updated November 2026, 2 days ago
Controlling apps accessing call history is still relevant policy #msintune
l let app access call history CSP
learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy
This policy setting specifies whether Windows apps can access call history.
You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access call history by using Settings - Privacy on the device.
If you choose the "Force Allow" option, Windows apps are allowed to access the call history and employees in your organization can't change it.
If you choose the "Force Deny" option, Windows apps aren't allowed to access the call history and employees in your organization can't change it.
Controlling apps accessing call history is still relevant policy #msintune
l let app access call history CSP
learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy
This policy setting specifies whether Windows apps can access call history.
You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access call history by using Settings - Privacy on the device.
If you choose the "Force Allow" option, Windows apps are allowed to access the call history and employees in your organization can't change it.
If you choose the "Force Deny" option, Windows apps aren't allowed to access the call history and employees in your organization can't change it.










