Skip to content

AI automation consulting · Microsoft 365

Microsoft 365: less manual work in your own tenant

We set up Power Automate, SharePoint, Teams and Outlook in your tenant, your own Microsoft 365 environment, so that approvals, documents and mailbox rules run without manual work. Some of it is already in your licences. What is missing, we tell you before you buy.

Request an AI checkSee the Copilot workshop
RequestReviewDraftApproval
Fig. 1.2From request to approval, inside your own tenant.

Runs in your tenant·Licence check before any purchase·Documentation for your IT

01Services

What we set up in your tenant

We start with what takes the most manual work off your team and expand from there.

  • Power Automate

    Flows

    Automatic workflows for approvals, notifications, documents and mailbox rules.

  • SharePoint

    Lists and approvals

    Requests, leave, expenses or orders as a list with status and history. Approval happens with one click in Teams.

  • Microsoft 365 Copilot

    Introduce Copilot

    Set roles, access and rules so that Copilot only draws on content each person is permitted to access. Optionally with a training for your team.

    See the Copilot workshop

02Typical flows

What Microsoft 365 can take off your hands

For these workflows the standard connectors for Outlook, Teams and SharePoint are often enough.

Example scenario

  • Approvals

    Approve leave and expenses

    Before
    The request goes to the manager as an email attachment, and the answer comes back at some point.
    After
    The request lands as an entry in a SharePoint list, the manager approves in Teams, and everyone can see the status.
    Stays with a person
    The manager decides.

  • Documents

    Generate quotes and contracts from a list

    Before
    Data is copied from Excel into a Word document.
    After
    The document is generated from the list entry and filed in the right place.
    Stays with a person
    A person checks the document before it goes out.

  • Outlook

    Read orders and requests

    Before
    Incoming mail is read and transferred by hand into the list or the system.
    After
    The key details are read out and created as a case.
    Stays with a person
    Unclear cases go to a person.

03Approach

From tenant check to rollout

We start with a review and only then build. After each step you decide whether to continue.

  1. Step 01

    Look at the tenant

    licence check before any purchase

    Licences, security settings and the tools in use. We look for unused automations and check whether your licences cover them.

    1/4 · ReviewResult

    A list of workflows, effort and missing licences.

  2. Step 02

    First flow

    fixed price, in writing first

    A Power Automate flow or a list with approval goes live. Scope and fixed price are agreed in writing beforehand.

    2/4 · PilotResult

    A running workflow in your tenant, tested in daily work.

  3. Step 03

    More workflows and Copilot

    after the pilot, on request

    We carry the approach over to further workflows and introduce Copilot with roles and rules. If you want, we train your team.

    3/4 · RolloutResult

    Several workflows run, and access and rules are set.

  4. Step 04

    Documentation

    operation monthly by agreement

    We document flows, lists and permissions so that your IT can maintain them. If you want, we keep looking after the solution.

    4/4 · HandoverResult

    Every flow is documented and has a named owner.

See the AI check

04Prerequisites

What we need to get started

Microsoft 365 tenant
An existing tenant with Exchange Online, SharePoint and Teams. Some flows need extra licences. We clarify that up front.
Access
An administrator account or a person who sets up permissions. We work with your IT or your Microsoft partner.
Contact person
Someone who knows the workflow and makes decisions.
Time
A workshop at the start and short check-ins during the pilot.

You buy licences from your own provider. We do not sell any.

05Your tenant

What stays in your tenant

  • 01Data and accounts stay with you

    Documents, lists and mailboxes stay in the tenant. Flows, lists and connections run under your accounts, and we keep no copy of your data of our own.

  • 02Roles and permissions

    Flows and Copilot only access content the person involved is permitted to see. We set the permissions beforehand with your IT. We sign the necessary agreements (DPA) before we start.

More on AI automation consulting

Common questions

Questions about Microsoft 365

Sometimes. Many useful flows get by with the standard connectors for Outlook, Teams and SharePoint. When a premium connector is needed, we tell you before you buy.

AI check

What is in your tenant?

In the AI check we look at which workflows you can automate with Microsoft 365 and what your licences allow.

Request an AI checkSee the Copilot workshop