If you’ve recently exported users from the Microsoft 365 admin center, you may have noticed that the CSV file format has changed. Missing columns, new field structures, and delimiter changes are causing confusion among IT admins worldwide. Here’s a breakdown of what’s different, why it matters, and how you can adapt your workflows.
What Changed in the Export Users CSV?
- Missing Fields – Key columns that were previously available no longer appear in the export.
- License Delimiter Removed – In the past, multiple licenses were separated by a “+” sign. This delimiter is gone, making license parsing inconsistent.
- UserStatus Variations – Guest accounts now show up as “Guest,” while some members are flagged as “Unlicensed,” even when they are part of the tenant.
These subtle changes can have a big impact on automation, reporting, and license audits.
Community Feedback: Real-World Impact
Microsoft 365 admins have been actively discussing these changes on the Tech Community forum.
- Broken Automations: Power Automate, Power BI, and Power Query flows had to be reworked to handle the new schema.
- Silent Rollout: The changes were introduced without official documentation, leaving IT teams scrambling to adjust.
- Underlying Cause: Experts suggest the change may be tied to Microsoft’s retirement of the MSOnline module (Get-MsolUser) in March 2025, with the new Graph API (Get-MgUser) becoming the standard.
Why It Matters
- Automation Disruptions – Scripts relying on consistent CSV structure may break.
- Reporting Issues – Missing fields complicate license audits and compliance reports.
- Future Shifts – With MSOnline deprecation approaching, further format changes are likely.
In short: if you depend on Microsoft 365 exports for reporting, you’ll need to update your tools.
How to Adapt: Workarounds & Solutions
1. Switch to Graph API
Move away from the admin center export and use PowerShell with Get-MgUser. This gives you control over which fields are exported and in what format.
2. Add Custom Parsing
If you must rely on the admin center export, consider adding a post-processing script to:
- Re-insert a consistent delimiter (e.g., “+”) for multiple licenses
- Normalize UserStatus values
- Re-add missing fields where possible
3. Build Resilient Automations
Design your Power Automate or Power BI flows to handle flexible input, detecting column changes instead of breaking when they occur.
4. Stay Informed
Keep an eye on Microsoft’s retirement roadmap and admin documentation to anticipate future changes.
Conclusion
The recent change to Microsoft 365’s Export Users CSV caught many admins off guard. Missing columns and formatting differences disrupted workflows, but the shift also signals Microsoft’s move towards Graph API as the new standard.
By updating scripts, adjusting parsing logic, and embracing Graph-based exports, IT admins can future-proof their reporting processes and avoid similar headaches down the road.
