arades License Suite · Microsoft license management

Manage tenants, roles, users and licenses.

The License Suite manages licenses across several Microsoft tenants — and those of every other vendor. Keep inventory, derive demand from roles, approve requests, change quantities, cancel and meet deadlines. arades carries out what you decide, as your licensing partner.

Manage

Tenants, departments, roles, users and licenses — in one place.

For one organization or for several. Every list can be filtered by tenant and by your own attributes.

Workstations in an office — Microsoft license management for several tenants with departments, roles, users and licenses in one place
6
areas you manage in one place

Manage tenants

Connect several Microsoft tenants, see the connection and administration status per tenant, switch between tenants or view them all at once. New tenants are requested in the portal.

Manage departments and cost centers

Create your own attributes — department, cost center, location — and split license quantities across them, for example twelve for sales and eight for IT. None of this is written to Microsoft.

Manage roles

Create roles with a license template: you define which Microsoft products and which third-party licenses belong to “Field Sales”. Several roles per person, each license counts once.

Manage users and staff

Reconcile people from Microsoft, additionally record staff without a Microsoft account, assign and change roles, handle joiners and leavers.

Manage other vendors’ licenses

Microsoft subscriptions and licenses from other vendors in the same inventory — with license model, quantity, contract number, term, notice period and automatic renewal.

Manage team and access rights

Define per person which tenants they see and what they may do: view, request, approve, order, administer. Per tenant and per right individually.

Control

Change quantities, switch automatic renewal, cancel.

For every Microsoft subscription you obtain through arades — from the portal, without going through support or a distributor. Only whoever holds the subscription can change it.

Meeting with documents at a table — changing or canceling Microsoft licenses in quantity, term and renewal
4
ways to act on every subscription

Change quantity

Add licenses or reduce them for the next renewal, with a note on the cancellation window.

Automatic renewal

Switch it on or off per subscription — visible in the inventory, not hidden in a setting.

Cancel

Cancel a subscription while the window is open. The portal shows the last possible day.

Term and billing

Monthly, annual or three-year, with monthly or annual payment — per subscription.

In the portal

Eight views, one license inventory.

Screenshots from the portal. All data shown is fictitious.

Microsoft license management across several tenants: tenant hub with connection status, administration role and ordering approval per tenant

Tenant hub. Connect, status per tenant, tenant switch, request a new tenant.

Optimize

The license optimizer checks your inventory for six types of finding.

Across all tenants at once, with a note on from what date a change takes effect.

Team at a conference table with laptops — the license optimizer checks licenses of several tenants for unused and doubly paid components
6
types of finding in the inventory

Unassigned licenses

Purchased, paid for, assigned to nobody — per product and tenant, with the next date on which the quantity can be reduced.

Doubly paid services

Per person: which services are paid for through two licenses at once. The overlap is reported as complete or partial; services switched off in Microsoft do not count.

Over-assigned subscriptions

More assigned than purchased. Microsoft can block the affected users — the portal reports the case before it happens.

Wrongly sized plans

Anyone on a large plan who uses only what a smaller one already covers. The basis is the usage report from Microsoft.

Objects that need a license but have none

Shared mailboxes that require a license because of their size or an enabled archive, room and resource mailboxes, service accounts, guest accounts, accounts that have never signed in.

The same person in several tenants

Anyone working for two companies often holds two full licenses. Only an inventory that brings all tenants together produces this finding.

Licenses of several tenants split by department: twenty licenses distributed across sales and IT, as a column and a filter

Assign

Derive license demand from roles — assign across tenants.

You give a person a role; the suite determines the demand from that role’s license template and reconciles it against the existing inventory — in the tenant the person belongs to.

  • A free third-party license exists: it is assigned immediately.
  • None free: a procurement note is created.
  • Microsoft, quantity available: an assignment task is created.
  • Microsoft, quantity missing: ordering demand, bundled per tenant and product.

If a role is removed or a person leaves, the assignments that came from roles are released and the Microsoft license is reported as “becoming free”. Assignments made by hand remain untouched.

Request and approve

Software demand from business departments, with an approval path instead of email.

Open-plan office with workstations — departments request licenses through the portal, the widget or a role
3
ways demand comes in

Three ways in

A request in the portal, a request through a widget in the intranet or SharePoint with sign-in via a Microsoft account, or automatically from a role.

Up to three approval stages

Line manager, department owner, license management. Anyone who requested it themselves or has already decided does not decide again.

A selection per department

You define which software is offered to a department — optionally restricted to exactly that selection.

A purpose is mandatory

Every request states a purpose. Every decision is recorded with person, time and note in the history.

Approval emails

On request, an email to the approver and the outcome to the requester. The decision is made in the suite.

Waiting list for licenses becoming free

When a license becomes free, it is offered to the oldest matching request — instead of buying what will be free in three days anyway.

Deadlines and decisions

The cancellation window, not just the renewal date.

Every overview carries the date. What counts is the last day on which a change still takes effect.

Everyday work in an open-plan office — license management with cancellation windows and renewal dates across all tenants
1
day on which the change still takes effect

Deadlines across all tenants

Renewals of Microsoft subscriptions and third-party contracts in one list, with notice period and dates that have passed.

Reminder and escalation

An email at the deadline, a second and third stage, a deputy. A deadline that passes without a decision creates an entry.

Record the decision

For every finding: act on it, defer it or discard it — with a reason. The decision is stored and not recalculated on every visit.

Execute on the date

“Act on it” receives an execution date inside the cancellation window. On that date we reduce the subscription and confirm it to you.

License news

Microsoft changes, related to your own inventory.

Price changes, discontinued products, new plans, changed licensing rules and expiring transition periods — put in context by us, not forwarded.

Workstation with documents and a screen — reading and interpreting Microsoft changes for your own license management
1
field decides: action needed

It affects you, or it does not

Every item is linked to products. The portal uses that to determine how many of your licenses are affected, and in which tenants.

Action needed: yes, no, check

The most important field of every item. The dashboard shows only those items that call for action and touch your inventory.

Deadlines become dates

When a transition period ends, a date appears in your deadline list — not just a note buried in prose.

Access

Rights in stages, each stage with its own consent.

The application does not request its rights in advance, but only when you want to use the corresponding function. Each stage is a separate application with its own consent in your tenant.

Connecting

A single read right: tenant name, license inventory, terms. Only a global administrator in your tenant may connect.

People

Seeing who holds which license requires a second, separate consent. Until then the application sees no person at all.

Log and verification

Every call with purpose, result and identifier, chained and exportable as CSV. You will find that identifier again in your own Microsoft logs.

Disconnecting

One click: the calls stop, all stages are reset, your tenant data held by us is deleted.

Support ticket towards Microsoft from license management: status, Microsoft ticket number and history

Support

Support tickets towards Microsoft, from the portal.

Anyone who obtains Microsoft through a partner cannot open their own ticket in the Microsoft 365 admin center — that is Microsoft’s rule, not a setting. That makes us your point of contact, and the portal is the way in.

A ticket with tenant, service, urgency and description. The status separates “with arades” from “with Microsoft” including the ticket number — it only says “submitted” once that number exists. History and replies remain readable in the portal.

Next step

Connect one tenant and look at your own inventory.

The connection is read-only and is granted by a global administrator of your tenant. You can disconnect at any time with one click.

Demo

60 minutes with your own license inventory.

One connected tenant is enough. We walk through your inventory, your deadlines and your findings.

Frequently asked questions

What prospects ask first.

01Do we have to move our licenses to arades?

Not for inventory, roles, requests and deadlines — every tenant can be connected read-only, regardless of where the licenses were bought. Changing quantities, canceling and carrying out changes on the agreed date require the subscription to run through us: only whoever holds it can change it.

02Which rights does the application get in our tenant?

On connecting, a single read right: purchased licenses, terms, tenant name. For people and assignments you grant a second, separate consent. The application does not request usage reports or Microsoft messages at present. Only a global administrator may connect.

03Can we assign licenses in the portal?

Allocation through roles and the target-actual check run in the portal. The actual assignment in Microsoft is carried out with your own permissions and appears under your name in your logs — the suite does not write to your directory.

04Does this also work for software that does not come from Microsoft?

Yes. You record third-party licenses with license model, quantity, contract, term and notice period and assign them to people. They appear in the same inventory, in the same role templates and in the same deadline list as the Microsoft subscriptions.

05How current are the figures?

As current as the last reconciliation. You trigger it per tenant; inventory, assignments and dates then reflect that state. Every view states the time at which it was read.

06How does demand from the departments come in?

Through the portal, through a widget in the intranet or SharePoint with sign-in via a Microsoft account, or automatically from a role. Every request states a purpose, every decision is recorded with person and time in the history.

07Does everyone on the team see the same thing?

No. Per person you define which tenants they see and what they may do — view, request, approve, order, administer, per tenant and per right.