Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

JackDDavis/MEMCustomCompliance

Open more actions menu

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

66 Commits
66 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

MEMCustomCompliance

With the availability of Custom Compliance, customers now have the ability to further define what device compliance means for their organization's managed Windows devices. Depending on your Custom Compliance use case, this can become quite the task. Manually building the correctly formatted JSON can be an error prone process. To assist with this, we are providing a PowerShell module for Custom Compliance. Today, the module consists of 2 cmdlets:

  1. New-IntuneCustomComplianceSetting cmdlet can be used to properly format an individual setting. This cmdlet will provide the JSON export required for upload.
  2. New-IntuneCustomComplianceRuleSet cmdlet can accept more complex multi-property queries and output and transform each setting and its value into a JSON ruleset that can be imported into Intune.

ReleaseNotes:
*1.1.1 - Language ValidationSet & error handling for periods in SettingName (Latest)
*1.1.0 - CustomQueryResult Parameter set for hashtable handling
*1.0.1 - Code cleanup and Unit test improvements
*1.0 - Initial stable Release

About

Official Repository of the IntuneCustomCompliance module in PowerShell Gallery

Topics

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages

Morty Proxy This is a proxified and sanitized view of the page, visit original site.