SOLVED

Broken dynamic membership rules of Autopatch managed groups?

Brass Contributor

Hi,

 

I found these two dynamic groups in AAD seems have a broken membership rule:

Alber_0-1667197637781.png

 

Devices registered with Autopatch are still not be assigned to them:

Alber_1-1667197838630.png

Alber_3-1667197902168.png

Alber_5-1667198094903.png

 

Did I miss something, or these two groups are indeed broken?

 

Thanks anyway.

3 Replies
Hi i have opened ticket for his on MS.
Looks there is problem in dynamic query
-contains "Microsoft365Managed_".
MS is working on fix. I hope :)

@Marek_Belan

Thank you.
And I found a post in May indicating the same problem:
POST 

 

Seems the mystery "Microsoft365Managed_" persists.

Waiting for fix.

best response confirmed by Alber (Brass Contributor)
Solution
Hi @Alber, @Marek_Belan, we are currently updating the Autopatch configuration to resolve this issue. The deployment of the change commenced last week and will continue this month. Please see MC443898 "Migrating from OMA-URI policies...." in Message Center for more details.
1 best response

Accepted Solutions
best response confirmed by Alber (Brass Contributor)
Solution
Hi @Alber, @Marek_Belan, we are currently updating the Autopatch configuration to resolve this issue. The deployment of the change commenced last week and will continue this month. Please see MC443898 "Migrating from OMA-URI policies...." in Message Center for more details.

View solution in original post