ES
All services

dForts services

AI, automation and custom applications in Microsoft 365, security first

Copilot, agents, automations and applications built for your process, not the other way round. Deployed so that AI only sees what each person is meant to see.

Discuss a use case

Who it is for

Businesses that want to get value from Copilot and automation without the first result being the AI showing the manager's payslip to everyone. Copilot finds everything a user can see; if permissions have gone unreviewed for years, that is a lot. That is why we start with security.

What we do

  • Copilot readiness. Review of permissions and sharing in SharePoint and OneDrive, sensitivity labels, which data is ready and which is not. Without this step we do not recommend switching Copilot on.
  • Microsoft 365 Copilot rollout. Licensing, a pilot group, use cases per department and training so it actually gets used.
  • Copilot Studio agents. Assistants that answer from your documentation (procedures, policies, catalogue) or take actions: look up an order, open a ticket.
  • Automation with Power Automate. Approvals, notifications, integration between tools, processes that today run on email and Excel.
  • Custom applications. Embedded in SharePoint (SPFx), inside Teams or standalone. Built with Power Apps and Dataverse when that fits, or as custom development on Microsoft Graph when more is needed. Fully tailored to the client's process, with AI where it adds value (Copilot, agents, Azure OpenAI) and the same permissions and labels as the rest of the tenant.
  • From the shared spreadsheet to an application. Forms, job sheets, inventories, requests, approvals: when the spreadsheet cannot take any more, with governed data available on mobile.
  • Governance. Who can create what, with which connectors, and how it is controlled. So automation does not become the next security problem.

How we work

  1. One concrete use case. We start with a process that hurts: the one that eats the most time or causes the most errors.
  2. Permissions and data first. We check what the AI will see before giving it access to anything.
  3. Pilot, measure, expand. A small group, measured results, and only then a wider rollout.

Real cases

An agent that answers the usual questions

A services company received the same internal questions every day: how to request leave, which expenses can be claimed, where a given template lives. A Copilot Studio agent connected to their SharePoint answers them in Teams, with the source linked. HR got hours back every week.

Invoice approvals without lost emails

Supplier invoices landed in a mailbox and were approved by replying to the email, or not. With Power Automate every invoice enters a flow with an owner, a deadline and reminders, and is logged in SharePoint. No forgotten invoices since.

Job sheets on the phone instead of paper

Technicians at an installation company filled in paper job sheets and someone typed them into Excel at the end of the day. A mobile Power App, with signature and photo, feeds invoicing directly.

An internal requests portal inside the intranet

A company handled requests to admin (leave, equipment, access) by email. We built an SPFx web part in their SharePoint intranet, also available as a Teams tab, where every request is logged, classified by AI and routed to whoever resolves it, with a deadline. Same interface as the rest of the intranet: nobody had to learn anything new.

Frequently asked questions

Does Copilot see my data? Does it train on it?

Copilot works with the data each user already has access to, inside your tenant, and Microsoft does not use it to train its models. The real risk is internal: a user seeing what they should never have been able to see. That is why we review permissions first.

Do I need a Copilot licence for everyone?

No. The usual approach is to start with a group that will get value from it and expand based on results. Many automations need no Copilot at all.

Does data leave the European Union?

Microsoft 365 lets you keep data in EU datacentres and Copilot respects that location. We verify it in your tenant.

How long until we see results?

A simple automation, days. An agent over your documentation, two to four weeks including permission preparation.

Can we maintain it ourselves afterwards?

Yes. We document and train whoever will maintain it, or we maintain it as part of tenant management.

Power Apps or custom development?

It depends on the case, and we tell you before starting. Power Apps quickly solves forms, flows and internal apps on Dataverse or SharePoint. When you need an interface embedded in the intranet, complex logic or integration with external systems, we build with SPFx, Teams Toolkit and Microsoft Graph. Either way the application is yours, lives in your tenant and inherits its security.

Which process would you like off your plate?

Tell us about one. We will say whether Copilot, an agent or an automation is the right tool, and what it would take to launch it securely.

Discuss a use case