What we need first
A basic inventory, who’s allowed to ask for what, working languages, how requests reach us, and what you’ve told the client is included.
Three kinds of work
Below are the three situations we handle most. Each one lists what we need from you upfront, what’s included, what’s not, and what you get back when it’s done.
For a client who needs a reliable way to handle everyday access, device, account, and collaboration-tool requests.
A basic inventory, who’s allowed to ask for what, working languages, how requests reach us, and what you’ve told the client is included.
What you get: A closed request with a result, anything still open, and a message you can send the client under your own name.
What we hand back: A resolution note in English, French, or both.
For an environment where account, licence, and configuration changes need someone actually watching them.
Access to the tenant, the right permissions, who owns which licences, and named admins on your side.
What you get: A clearer record of what changed in the tenant, and a short list of anything that needs your decision.
What we hand back: A change summary: what happened, why, and what to do next.
For a client who wants tighter everyday security practices - without you calling it a SOC.
The baseline you’re targeting, who owns security decisions, known exceptions, and who gets told about risk.
What you get: A short list of gaps written as decisions for you to make - not a wall of unowned alerts.
What we hand back: A baseline review with a requested decision, an owner, and a follow-up date.