Connect Copilot to your Fortnox.
Adding the connector itself takes about 5 minutes. The prerequisites — an Azure subscription, a billing plan and Power Platform permissions — take 30–60 minutes the first time and require administrator rights. In most organisations IT sets up the prerequisites, then you add the connector yourself. Note that Microsoft updates its interfaces continuously, so menus and buttons may look slightly different than in the video — the steps and principles stay the same.
https://fortnox-copilot.sidcom.ai/mcp The video shows how to add the connector as an MCP server in Copilot Studio, publish your agent to Microsoft 365 Copilot and sign in with Fortnox. It assumes the prerequisites in the checklist below are already in place — check those first.
Open Copilot Studio →- Company info
- Customers
- Suppliers
- Articles
- Invoices
- Supplier invoices
- Quotes
- Orders
- Bookkeeping
- Payments
- Settings
- Archive
- Inbox
- File links
- Currency
- Payroll
You choose which modules Copilot may use, based on your licenses. Built by Sidcom, not by Fortnox or Microsoft. Read the user agreement.
// who_does_what
Two roles, one setup.
- 01
IT administrator (Microsoft)
Sets up the Azure subscription, the billing plan for your Power Platform environment, permissions, and any admin approval in Teams. 30–60 minutes the first time. Not familiar with Power Platform Admin Center and Azure? Send this page to whoever runs your Microsoft environment.
- 02
You, the user
Adds the connector in Copilot Studio, publishes the agent and connects your own Fortnox account. About 5 minutes.
// before_you_start
Check these two things first.
- 01
Credits for Copilot agents in Microsoft
Your Power Platform environment needs either users with a Microsoft 365 Copilot license, or a pay-as-you-go billing plan linked to an Azure subscription. Check in the Power Platform Admin Center under Licensing → Billing plans — an active plan should be listed with your environment connected.
- 02
Permission to create connectors
Your user must be allowed to create custom connectors in the environment. Easiest to check by trying — if you hit a permission error when adding the connector, contact IT.
Common setup errors, solved.
"You need credits to continue. This environment doesn't have credits available right now."
Your Power Platform environment has no credits to run the agent. Two ways forward. Pay-as-you-go (most common for smaller organisations): in the Power Platform Admin Center, go to Licensing → Billing plans → New billing plan, link the plan to an Azure subscription and a resource group, pick the Copilot Studio meter (Dataverse is included automatically) and connect your environment. Or a Microsoft 365 Copilot license: users with a full Copilot license have agent usage included. Note: once the plan shows Enabled it can take up to an hour to apply, and only new chats pick up the change — existing threads keep the old status. This step is normally handled by IT.
"Failed to create MCP server. Please try again."
Usually one of two causes. Wrong authentication: the connector uses OAuth, so if Authentication is set to None the creation fails — choose OAuth 2.0 → Dynamic discovery. Or a name conflict from an earlier attempt: an interrupted try can leave a half-created connector behind. Give the server a unique name, and/or delete old Fortnox connectors first (see the DeleteAccess question below), then try again.
Fortnox says a license is missing when I approve the connection
The company you're connecting to does not have the connector activated. Activate it for that company and the connection goes through.
The agent doesn't show up in Copilot after publishing
Ticking Make agent available in Microsoft 365 Copilot only makes it available — it isn't installed automatically. In the publish dialog, click See agent in Microsoft 365 (or See agent in Teams) to install it for yourself. Clients don't always fetch new agents right away: log out and back in to Teams, or refresh the browser. For colleagues, use Availability options; organisation-wide rollout requires admin approval in the Teams admin center. Your tenant must also allow Power Platform apps in Teams — that setting is managed by IT in the Teams admin center.
"The user … does not have sufficient access rights … Required access right 'DeleteAccess' is missing."
You're trying to delete a custom connector that someone else owns — in Power Platform, everyone can only delete their own connectors. Ask the owner to delete theirs, or have a Power Platform administrator do it. If the old one doesn't have to go, it's enough to give your new connector a unique name.
"No Azure subscriptions available" when I create a billing plan
Pay-as-you-go is billed against an Azure subscription, and there is none in your tenant — or your user can't access it. Create one at portal.azure.com under Subscriptions → Add (e.g. Pay-As-You-Go). Make sure it's in the same tenant as your Microsoft 365 and that you have the Owner or Contributor role on it. This step is normally handled by IT.
The resource group doesn't appear in the billing plan dialog
The fields depend on each other — the resource group list only fills in after you've chosen an Azure subscription. Pick the subscription at the top and the resource groups appear. If the subscription has no resource groups, create one at portal.azure.com → Resource groups → Create. If the subscription doesn't show at all, register the Microsoft.PowerPlatform resource provider on it (Subscription → Resource providers → search → Register) and refresh the page.
My environment doesn't show up in the billing plan ("No environments")
The list filters by region, and the region refers to where the environment is provisioned — not where the company is. The default environment ("[Company] (default)") usually sits in the Europe region, even for Swedish organisations. Switch Region to Europe (or search for your company name) and the environment appears.
A "Permission Required" card appears when I ask a question
This is not an error. The first time the agent calls the connector, Microsoft asks you to approve it — part of their security model. Click Allow and the agent continues. The card can reappear after updates to the agent.
Still stuck?
The Microsoft prerequisites involve several moving parts and are handled by IT in most organisations — take help from your IT administrator for Azure, the billing plan and permissions, and send along a link to this page. Prefer a simpler setup? Our Claude Fortnox Connector connects in a couple of minutes without Copilot Studio. Otherwise contact us — we reply fast.