From a 30-minute call to a working solution in your tenant
We start with a 30-minute call, after which we send a fixed price for a read-only check or a pilot in writing, excluding VAT, and we deploy the solution in your Microsoft 365 and Azure tenant together with your IT team.
How a project runs · illustrative example
- 30-minute call
- Check or pilot
- Rollout
- Support
Pilot proposal
- Scope
- Described in writing
- Price
- Fixed, excluding VAT
- Access
- Only what is needed
01
How the work runs
01
A 30-minute call
We find out where your documents are kept, who administers Microsoft 365 and what you want to achieve. It helps to bring your IT administrator. The call is free and commits you to nothing.
02
A proposal in writing
We send the scope, the list of permissions needed with the reason for each, and a fixed price excluding VAT.
03
A check or a pilot
A read-only check shows where you stand and changes nothing. A pilot covers one process and a small group of people, so you see the result before deciding on a wider rollout.
04
Rollout in your tenant
We deploy the apps in your Azure subscription together with your IT team. Your administrator approves the permissions; we prepare the steps and the scripts.
05
Tuning and handover
After the first runs we fit the rules to your real file names and folders, and hand the documentation over to your IT team.
06
Support
If you need it, we agree ongoing support: watching for errors, updating rules and keeping up with Microsoft changes.
02
Price
We do not publish a price, because it depends on scope: how many people, folders, rules and systems the work covers. After the call we send a fixed price in writing, excluding VAT. If the scope does not change, neither does the price.
Microsoft bills you directly for the Azure resources. We estimate them in the proposal, so you know the figure in advance.
The price of later stages is confirmed after the pilot, once we have seen how the solution works with your data.
04
What we need from you
- A description of the process or the list of required documents
- An administrator who can approve the permissions: a Global Administrator or Privileged Role Administrator
- An Azure subscription and a resource group in an EU region; for setup you can grant us temporary rights on that group only and remove them afterwards
- A shared mailbox, if you want email reminders
- A Teams administrator, if you want a Teams bot
- Two short review meetings during the pilot
Common questions.
Something else on your mind?
How much does Microsoft 365 automation cost?
The price depends on scope, so we do not publish one. After a 30-minute call we send a fixed price for the check or the pilot in writing, excluding VAT. Microsoft bills you directly for the Azure resources.
Is the call free?
Yes. The 30-minute call costs nothing and commits you to nothing.
How long does a pilot take?
We state the length in the proposal. It depends mostly on when we receive the process description, your answers and IT access, so we count our working time from that day.
How much time will our IT team need?
In our test environment, a script registered the app and granted consent in under a minute. The Exchange right takes longest: in our test it took about two hours to take effect, so we set it up a day early.
Can we start with the check only?
Yes. The read-only check is a separate piece of work: it shows where you stand and changes nothing. Afterwards you can decide whether to continue with a pilot or make the changes yourselves.
Do you work with our IT provider?
Yes. If an outside IT company administers your Microsoft 365, we prepare the steps for them and help them carry them out remotely.
What happens after the pilot?
You decide: extend, change or stop. If you stop, you remove access by following the handover document, and our solution no longer runs in your tenant.