Forum Discussion
Cloud Policy Service needs a Powershell module
I just started using the Cloud Policy service capability in the config.office.com portal. A Powershell module is sorely needed, in part because the UI a) can be slow and b) is uninformative in that the Policy Configuration Review/Summary is too high level and there is no comprehensive reporting of configured configurations and/or policies.
Cmdlets that could extract the configurations and for each configuration, it scope, the policies that are configured and their configuration setting; list of all policies and policy configuration where they are configured would be very useful.
Even better would be a cmdlet that can assess the policies applicable to a specific user and the 'route' the Cloud Policy Service took to determine them would be very useful in identifying why a particular behavior took place or didn't. This differentiate between device and web apps, where appropriate.
1 Reply
Totally agree on this. The config.office.com portal feels way too clunky when you're trying to audit applied settings or troubleshoot why a specific policy isn't taking effect for a user.
Right now there's no native dedicated PowerShell module for Cloud Policy Service, which is a pain. Most folks end up querying Graph API endpoints directly (under /beta/officeConfiguration or similar schema paths) via Microsoft Graph PowerShell to dump raw configurations, but it’s definitely not user-friendly out of the box.
If you haven't already, submit this via the Feedback button right inside the portal or upvote it on the Feedback Portal. Having cmdlets like Get-OfficeCloudPolicy with user-scoping features would save a ton of time for tenant admin work.
