As part of our continued commitment to strengthening security across Exchange Online, we want to inform our customers about an important change coming to the Exchange Online PowerShell module.
What...
Published Feb 12, 2026
Version 1.0
Blog Post
So, just to clarify, is this a client-side change then? Will older versions of the module still work with -Credentials, or are you going to block ROPC service-side at some point?
WRT to supported scenarios, there are few cmdlets that do not work with application context/MSI. What will be the alternative to manage those?
Also, what about the SCC cmdlets/connectivity method?
Nino_Bilic
Microsoft
MicrosoftI'll answer the first part of your question, Vasil (other parts someone else will). The changes made here are both client and service side:
- Yes, PowerShell modules starting with the version specified will not have that parameter, and you could after that day still use the older PS version with the Credential parameter. So yes, this is a client-side change.
- Also yes, there will be a service side change which will eventually break this no matter which client (PS version) you use on client side. And that change is the overall deprecation of ROPC flow. Once that goes, it's gone. Once that service change is made, no matter which version you have client side, the parameter will not work.