Licensing and cost review
Map plans and add-ons to the roles that need them. Check desktop apps, Teams, security controls and Copilot separately where applicable.
Get a Microsoft 365 setup that fits how your organisation works. AURUM helps you choose licences, plan a rollout or migration, and improve security and adoption in an existing tenant.
Microsoft Solutions Partner for Modern Work · Based in Nuremberg since 2014 · About AURUM
Start with licensing, a rollout, or an assessment of your current setup. We agree the scope with IT and business owners.
Map plans and add-ons to the roles that need them. Check desktop apps, Teams, security controls and Copilot separately where applicable.
Plan users, groups, roles and the workloads to deploy. Use a pilot to test actual work before opening access in stages.
Inventory mailboxes, file shares or SharePoint sites. Agree what to migrate, what to archive, and how to validate data and access.
Review sign-in controls, admin access, sharing and device requirements. See our identity and access management service.
Clarify where people work together, publish information and keep documents. Connect that design to ownership, training and support.
Review use cases, licences and access before a Copilot pilot. We can also agree ongoing support for an existing environment.
Compare the work each user needs to do, the controls the organisation needs and what is already licensed.
Compare Basic, Standard and Premium for users who need email, collaboration, apps or additional protection. Check the specific plan and market.
Assess these where scale, frontline use or governance requirements call for different capabilities. Verify any prerequisites before buying add-ons.
Check whether Teams is included in your offer and whether the intended Copilot features require separate licensing. Assign licences according to role and need.
Microsoft publishes Business plan comparisons and Microsoft 365 Product Terms. Review the offer available in your market.
A rollout is easier to approve when licensing, access and support decisions are documented.
See which users, licences, workloads and dependencies are in scope and what needs changing.
Test representative mail, files and permissions. Agree validation, support and who makes the go-live decision.
Agree who handles new accounts, policy reviews and support. See the AviloX Microsoft 365 support reference (German).
The rollout plan links technical changes to how teams will work on launch day.
Discuss your requirementsIdentify affected teams, current workloads and business deadlines.
Review licences, access, data and dependencies, then propose a target design and rollout plan.
Pilot representative users, verify critical workflows and move agreed content in stages.
Document the environment, train owners and agree support and review responsibilities.
Answers on licensing, migration and improvement projects.
Yes. We can review licences, user access, sharing, adoption and support, then suggest a sequence of improvements.
Compare user counts and roles, required security and compliance features, desktop apps and add-ons. We check these against what your organisation can buy and what it already owns.
Yes where dependencies and the migration plan allow. We assess which workloads can move, which need to coexist and how users will work during the transition.
Costs depend on user count, content volume, source systems, permissions, dependencies, testing and training. We review licence costs separately.
Yes. We can help check licences, choose pilot users, review access to business data and train people on relevant tasks.
Yes. We offer initial consultations in English and can discuss the requirements and operating model with your team.
Tell us whether you are planning a rollout, reviewing licensing or trying to improve an existing tenant. We’ll help you decide what to assess first.

Mustafa Yaylak
Managing Director, AURUM GmbH