How do I connect Billnado to Microsoft 365 Copilot?

Microsoft 365 Copilot uses a declarative agent to make Billnado MCP tools available. An administrator or integration developer configures and publishes this agent once. Users then select the Billnado agent in Microsoft 365 Copilot and sign in with their own Billnado account.

Requirements

• A Microsoft 365 environment with Copilot access and permission to upload custom apps.
• Visual Studio Code with Microsoft 365 Agents Toolkit 6.12.0 or later.
• An account permitted to provision or sideload the agent in the Microsoft 365 tenant.

Ask a Microsoft 365 administrator to check the tenant settings if Custom App Upload Enabled or Copilot Access Enabled is unavailable.

Create the declarative agent

1. Open Microsoft 365 Agents Toolkit in Visual Studio Code.
2. Select Create a New Agent/App.
3. Select Declarative Agent.
4. Select Add an Action, then Start with an MCP Server.
5. Enter https://mcp.billnado.be/mcp as the MCP server URL.
6. Select OAuth (with dynamic registration) as the authentication type.
7. Choose a location and give the agent a recognizable name, such as Billnado.

Billnado supports OAuth Dynamic Client Registration. You therefore do not need to create a separate client ID or client secret. The toolkit generates the plugin configuration with dynamic tool discovery enabled by default: Copilot fetches the available Billnado tools from the MCP server at runtime. You do not need to select tools manually. Tool discovery is separate from dynamic registration for OAuth.

Provision and use the agent

1. Sign in to Microsoft 365 from Agents Toolkit.
2. Open Lifecycle and select Provision.
3. Confirm provisioning and wait for the toolkit to finish.
4. Open Microsoft 365 Copilot Chat.
5. Select the new Billnado agent under Agents. During development, its name usually ends in dev.
6. Ask a Billnado question and select Sign in to Billnado when prompted.
7. Complete OAuth sign-in with your Billnado account.

For an organization-wide rollout, the administrator must publish the agent according to the organization's Microsoft 365 policies and assign it to the appropriate users or groups.

Administrations and access control

Every user signs in individually. Billnado applies the same access control as the regular application and uses that user's default administration.

Have the AI use subscribers_list to find the intended administration. Pass its selected ID as subscriberId on every subsequent administration-scoped tool call. This tool parameter replaces transport header configuration. Explicitly request subscriber_connect only if an accountant or support connection is still needed; your existing access rights continue to apply.

Billnado offers read and write actions. Check the administration, document and proposed consequences before making changes or sending anything. Use My licence in Billnado for licence changes; MCP supports only licence information and price calculations.

Verify the connection

Ask the Billnado agent, for example:

• “Which administrations can I access?”
• “Show the active license and usage limits.”
• “Find supplier Acme and show the contact details.”

When tools are out of date

With the default dynamic tool discovery, Copilot picks up new, changed and removed tools at runtime. Microsoft validates new and changed tools before making them available. Changes to Billnado tools alone therefore do not require republishing the agent.

If an expected tool is missing, ask the integration administrator to check which discovery mode the plugin uses. With dynamic tool discovery, the functions array in ai-plugin.json is empty and run_for_functions contains ["*"]. Also check whether the MCP server makes the tool available to the signed-in Billnado account.

If the integration administrator deliberately configured a fixed selection (pinned tools), the plugin contains a fixed tool list. To change that list or its included tool definitions, the administrator must update the manifest and resubmit the agent for validation and publishing.

See Microsoft: dynamic tool discovery and pinned tools for the differences and configuration.

Read Using Billnado through MCP for all tools and security guidelines. See the official Microsoft guide to building an MCP plugin for a declarative agent for tenant requirements, provisioning and publishing.