Company struggles after informally adopting M365 without policies
- A user in a small company is disconnecting their Windows OS account from Microsoft 365 due to company policy changes.
- The user is concerned about the implications for their Windows Subsystem for Linux (WSL) virtual machine during this process.
- Lack of documentation about the disconnection process leads to user uncertainty, but they feel confident in reinstalling Windows if necessary.
In a small company, which began using Microsoft 365 (M365) informally without mobile device management (MDM) policies, one user decided to log into their Windows operating system using their M365 account. Recently, the company has made the decision to deprovision their M365 services, which was not a choice made by the user. The user, who is one of two Windows users in the company, is contemplating the implications of this disconnection process. They are particularly concerned about their Windows Subsystem for Linux (WSL) virtual machine, which they believe might require reprovisioning after the disconnection. However, they are not overly anxious as most of their data is stored outside the laptop and they believe they can easily reinstall Windows if necessary. The user highlighted that there is a lack of documentation regarding the effects of disconnecting the M365 account from the Windows OS, leading them to seek information about what precisely happens when they click the disconnect button within the Access Work or School settings. This uncertainty regarding data preservation and application functionality serves to underline the challenges faced by users navigating the transitions imposed by administratively-driven changes in company IT policies, especially in contexts where MDM measures were never established.