Add Windows 365 Baseline #5699
Add Windows 365 Baseline #5699
Conversation
| Platforms = $enumPlatforms | ||
| RoleScopeTagIds = $getValue.RoleScopeTagIds | ||
| Technologies = $enumTechnologies |
There was a problem hiding this comment.
$enumPlatforms and $enumTechnologies are not defined.
| if ($CurrentValues.Ensure -ne $Ensure) | ||
| { | ||
| Write-Verbose -Message "Test-TargetResource returned $false" | ||
| return $false | ||
| } |
There was a problem hiding this comment.
Please remove this Ensure check. The handling of Ensure is done in Test-M365DSCParameterState on line 1848.
| # IntuneSecurityBaselineWindows356 | ||
|
|
||
| ## Description | ||
|
|
||
| Intune Security Baseline Windows356 |
There was a problem hiding this comment.
Windows356 instead of Windows365
| "resourceName":"IntuneSecurityBaselineWindows356", | ||
| "description":"This resource configures an Intune Security Baseline Windows356.", |
There was a problem hiding this comment.
Also Windows356 instead of Windows365
|
|
||
| node localhost | ||
| { | ||
| IntuneSecurityBaselineWindows10 'mySecurityBaselineWindows365' |
There was a problem hiding this comment.
Example does not match expected resource: IntuneSecurityBaselineWindows365
|
|
||
| node localhost | ||
| { | ||
| IntuneSecurityBaselineWindows10 'mySecurityBaselineWindows365' |
There was a problem hiding this comment.
Example does not match expected resource: IntuneSecurityBaselineWindows365
|
|
||
| node localhost | ||
| { | ||
| IntuneSecurityBaselineWindows10 'mySecurityBaselineWindows365' |
There was a problem hiding this comment.
Example does not match expected resource: IntuneSecurityBaselineWindows365
nee-source
force-pushed
the
feat/windows-365-baseline
branch
from
73a182e to
8ea2209
Compare
nee-source
force-pushed
the
feat/windows-365-baseline
branch
from
8ea2209 to
cdb98cd
Compare
|
@NikCharlebois PR review for your review. I co-authored the resource and checked its functionality. All good from my side. |
Pull Request (PR) description
Add Intune Security Baseline for Windows 365.
please note: does not yet work because of nested cim instance escaping of double quotes. @FabienTschanz is aware of it
This Pull Request (PR) fixes the following issues
Task list
Entry should say what was changed and how that affects users (if applicable), and
reference the issue being resolved (if applicable).