A useful Microsoft 365 review starts with the people using it, the subscriptions in place and the person responsible for each account. Gather that picture before deciding whether the next step is a license change, configuration review or different support arrangement.
Use the questions below to prepare a discussion with your current or proposed provider. Keep the exact products, account setup and responsibilities in view.
List the work people need to do.
Record the applications and shared information each team uses. Note recurring problems, planned staff changes and tools that sit outside the current environment. Separate a missing function from a problem with access, configuration or responsibility.
When comparing plans, ask the provider to check the current terms and included features against those requirements. Keep the plan name and any assumptions with the proposal so the comparison can be reviewed.
Identify the account and support owners.
Who controls the tenant, domain, billing and administrator access? Who approves staff changes, and who handles a problem that spans an account, a device and the network?
Record the responsible people or providers, not passwords. Arrange an appropriate transfer method if access later needs to change. An initial website inquiry does not need administrator credentials or confidential files.
Ask what a proposal includes.
- Which users, accounts and applications are covered?
- What review or setup work is included, and what remains separate?
- Who is responsible for access, data handling and recovery arrangements?
- What hours, escalation route and response commitments are actually agreed?
- What documentation and ongoing ownership are included at handoff?
If a change involves moving information, ask how the source will be checked, how a trial will be evaluated and who approves the changeover. The answers should refer to your environment rather than a general promise that everything will work together.
For LVC's broader support discussion, see Managed IT and IT Support. Confirm the specific Microsoft responsibilities as part of that conversation.