Community Q&a

Ask the Experts: Microsoft 365 License data in Flexera One

Date/Time: Wednesday 10th June 2026 3.30pm - 4.30pm BST/10.30am-11.30am EST

We’re launching a new Ask the Experts Community Q&A focused on common Microsoft 365 License data questions in Flexera One Saas Manager. During the scheduled Q&A window, Flexera experts will be available in the community to answer customer questions directly within the Q&A thread.

Please note this is not a webinar, there is no registration required – simply log into the community and participate in the Q&A thread during the scheduled window.

Our first topic will be on Microsoft 365 License data in Flexera One: Specifically, situations where things don’t quite line up e.g license counts don’t match expectations, users appear unlinked, or data just doesn’t look right

How it works

• Submit your question ahead of time using the form below
• Return to the Q&A thread in the Flexera Community on Wednesday 10th June during the scheduled Q&A window
• Flexera experts will respond directly in the Q&A thread
• Pre submitted questions will be prioritised.

Submit your question here [Submission link]

What you can ask in this session

 Topics related to Microsoft 365 License data on Flexera One Saas Manager

1.   How Microsoft 365 data should flow

2.   Expected behaviour: When to investigate vs expected behaviour

3.   How to spot if there is any missing or mismatched data

4.   How to quickly sanity-check Microsoft 365 license totals, assigned seats, and “consumed” numbers in Flexera One

Expert Panel:

• Dawn Hoagland, Senior Solutions Architect -Flexera
• Brad Akhers, Senior Solutions Architect -Flexera
• John Suehr, Solutions Architect- Flexera
• Toby Ivens Senior Solution Architect- Flexera

Submit a question: [Submission link]

Questions submitted by 5th June 2026 are more likely to be covered during the discussion.   If you’d like a calendar reminder, you can request one in the form.

The discussion thread will remain open throughout the session for follow up questions and conversation.