You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My tenants seem to have the associated cmdlets *-ClientAccessRule disabled even after granting the role Organization Client Access to my account, also tested through a Service Principal, therefore I cannot test this resource.
After digging a little bit in the interwebs it looks like CARs are going to be removed (in fact they should have been years ago) this next September, see [0], so I propose we also remove EXOClientAccessRule during the next breaking change.
The term 'Get-ClientAccessRule' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Same error appears for'New-ClientAccessRule' and 'Remove-ClientAccessRule'.
Environment Information + PowerShell Version
Win11 / PS5.1
The text was updated successfully, but these errors were encountered:
Description of the issue
My tenants seem to have the associated cmdlets *-ClientAccessRule disabled even after granting the role
Organization Client Access
to my account, also tested through a Service Principal, therefore I cannot test this resource.After digging a little bit in the interwebs it looks like CARs are going to be removed (in fact they should have been years ago) this next September, see [0], so I propose we also remove
EXOClientAccessRule
during the next breaking change.[0] https://techcommunity.microsoft.com/t5/exchange-team-blog/update-deprecation-of-client-access-rules-in-exchange-online/ba-p/3790165
Microsoft 365 DSC Version
1.24.710.3
Which workloads are affected
Exchange Online
The DSC configuration
N/A
Verbose logs showing the problem
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: