Repository navigation
Conversation
The Trellix Mobile Security entry was missing the leading 7 of its ID, so a Trellix connector was shown by its raw ID. The correct ID, 74873197-ffec-4dfc-9816-db65f34c7cb9, was read from Graph after creating the connector in a tenant. Also point the source comment at the right Microsoft365DSC resource and note where the table differs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Entire-Checkpoint: 01M710786Z860FPYCCHA5A1TKY
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Up to standards ✅🟢 Issues
|
Description
MT.1098 names each Mobile Threat Defense connector from a table of partner IDs. The Trellix Mobile Security entry was
4873197-ffec-4dfc-9816-db65f34c7cb9, seven characters in its first block, so it could never match and a Trellix connector was shown by its raw ID. julien-ly spotted this on #2736. Pass/fail was not affected.74873197-ffec-4dfc-9816-db65f34c7cb9, read fromdeviceManagement/mobileThreatDefenseConnectorsafter creating the connector in a tenant (Microsoft365DSC has the same typo).c2b688fe-48c0-464b-a89c-67041aa8fcb2, the ID Graph returned in a tenant in 🪲 MT.1098 does not consider policies that is ready for deployment but is first enabled after first registration #2595. Microsoft365DSC'se6f777f8-e4c2-4a5b-be01-50b5c124bc7fhas not been seen from a tenant.MSFT_IntuneMobileThreatDefenseConnectorresource instead of a Windows 10 device configuration resource, and notes where the table differs from it.Validation
./powershell/tests/pester.ps1: 8430 tests, no failures.🤖 Generated with Claude Code
Summary by CodeRabbit