We will be retiring the Revoke-SPOUserSession PowerShell cmdlet for Microsoft SharePoint Online (SPO), as part of our ongoing efforts to enhance security and streamline scope and permissions for our users. Instead, please use the Revoke-MgUserSignInSession, where we will continue to invest resources.
[When this will happen:]
We will begin rolling this out in early November 2024 and expect to complete by mid-November 2024.
[How this will affect your organization:]
Our telemetry indicates that only a few organizations are active users of the Revoke-SPOUserSession cmdlet for their user management needs. If your organization is currently using this cmdlet, transition to utilizing ‘Revoke-MgUserSignInSession’.
After the retirement, requests using the Revoke SPOUserSession cmdlet will be blocked with an error message similar to:
“This cmdlet has been deprecated and replaced by Microsoft graph cmdlet ‘Revoke-MgUserSignInSession’ as described in: Revoke-MgUserSignInSession
[What you need to do to prepare:]
Please immediately begin transitioning from using the Revoke-SPOUserSession cmdlet. To avoid unexpected impact, also ensure none of your workflows are calling this cmdlet. Instead, please use the Revoke-MgUserSignInSession, <Revoke-MgUserSignInSession> where we will continue to invest resources.
Additional Information:
Source: Microsoft
The upcoming retirement of the “Revoke-SPOUserSession” PowerShell cmdlet in Microsoft SharePoint Online (SPO) starting November 2024 will have an impact on both admins and users. Admins will need to transition to using the “Revoke-MgUserSignInSession” cmdlet for user management needs. This change is part of Microsoft’s efforts to enhance security and streamline permissions for users.
For admins, it’s essential to start transitioning from the old cmdlet to the new one to avoid any unexpected disruptions. Make sure to check your workflows to ensure they are not calling the deprecated cmdlet. Remember, Microsoft will continue to invest resources in the new cmdlet, so it’s a step towards improved user management.
As for users, they may experience a smoother and more secure authentication process once admins make the transition. So, while change can be daunting, it’s ultimately for the better!
In terms of criticality, this update is important for organizations using the deprecated cmdlet. It’s crucial to act promptly to avoid any disruptions in user management processes. So, grab your virtual toolbox and start updating those scripts!
Remember, change is the only constant in the tech world, so let’s embrace this update with a smile and a can-do attitude!