Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EXOClientAccessRule: Remove in next breaking change release? #4894

Open
ricmestre opened this issue Jul 16, 2024 · 0 comments
Open

EXOClientAccessRule: Remove in next breaking change release? #4894

ricmestre opened this issue Jul 16, 2024 · 0 comments

Comments

@ricmestre
Copy link
Contributor

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

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant