check before: 2024-11-01
Product:
Entra, SharePoint
Platform:
Online, World tenant
Status:
Change type:
Admin impact, Retirement
Links:
Details:
Summary:
The Revoke-SPOUserSession cmdlet for SharePoint Online is retiring in November 2024. Users should transition to using Revoke-MgUserSignInSession. The rollout starts early November and finishes by mid-November. After retirement, attempts to use the old cmdlet will result in an error directing to the new cmdlet.
Details:
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.
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2024-10-03
updated:
2024-10-03
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
summary for non-techies**
XXXXXXX ... free basic plan only
Direct effects for Operations**
Cmdlet Retirement Impact
After the retirement of Revoke-SPOUserSession, any attempts to use this cmdlet will result in an error, disrupting user management workflows.
- roles: IT Administrator, SharePoint Administrator
- references: https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.users.actions/revoke-mgusersigninsession?view=graph-powershell-1.0
Workflow Disruption
Existing workflows that rely on the Revoke-SPOUserSession cmdlet will fail, potentially leading to unauthorized access if not transitioned in time.
- roles: IT Administrator, Business Analyst
- references: https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.users.actions/revoke-mgusersigninsession?view=graph-powershell-1.0
User Access Management
Organizations that do not transition to Revoke-MgUserSignInSession may face challenges in managing user access effectively, leading to security risks.
- roles: IT Security Officer, Compliance Officer
- references: https://learn.microsoft.com/entra/identity/users/users-revoke-access
Training and Adaptation
Users and administrators will require training on the new cmdlet, which may lead to temporary inefficiencies during the transition period.
- roles: IT Trainer, End User
- references: https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.users.actions/revoke-mgusersigninsession?view=graph-powershell-1.0
Increased Support Requests
The transition may lead to an increase in support requests from users encountering issues with the new cmdlet, impacting IT support resources.
- roles: Help Desk Technician, IT Support Manager
- references: https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.users.actions/revoke-mgusersigninsession?view=graph-powershell-1.0
Configutation Options**
XXXXXXX ... paid membership only
Potentional Risks**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
explanation for non-techies**
In the world of Microsoft SharePoint Online, a specific tool called the Revoke-SPOUserSession cmdlet is being retired in November 2024. This cmdlet is like a key that administrators use to end a user's session or access to SharePoint Online. Imagine you have a special key that locks a room where sensitive documents are kept. If someone leaves the company or loses their right to access the room, you would use this key to lock them out immediately. The Revoke-SPOUserSession cmdlet works in a similar way for digital access.
However, Microsoft is replacing this key with a new one called Revoke-MgUserSignInSession. This new cmdlet is part of a broader system called Microsoft Graph, which is like a universal keyring that manages access across various Microsoft services, not just SharePoint. Think of it as upgrading from a single key to a master key that can lock and unlock multiple doors in a building, making it more efficient and secure.
The transition will begin in early November 2024 and finish by mid-November. After this period, trying to use the old cmdlet will result in an error message, much like trying to use an outdated key that no longer fits the lock. Organizations that currently use the old cmdlet should start planning to switch to the new one to ensure smooth operations and avoid disruptions.
For those managing user access, it's important to update any automated processes or workflows that rely on the old cmdlet. This change is part of a broader effort to enhance security and streamline user management across Microsoft's services. For more detailed guidance on how to make this transition, Microsoft provides resources and documentation online.
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
Last updated 1 month ago