WorkIQ MCP Tools no longer working with Agent 365 AI Teammates built in n8n

[pdwarf]

Description

Up until recently, the process to build a new Agent Blueprint that can be used for AI Teammates built with n8n was to run:

1. a365 init, then
2. a365 develop add-mcp-servers mcp_M365Copilot mcp_CalendarTools mcp_MailTools mcp_SharePointRemoteServer mcp_OneDriveRemoteServer mcp_TeamsServer mcp_WordServer, then
   3.a365 setup all

This would eventually create a blueprint like below, with all the relevant WorkIQ Tools permissions, like so:

Now with the latest CLI changes, the process seems to be restrict a Blueprint to max 10 inheritable permissions, which prevents successfully running a365 setup permissions mcp, see console output below:

Hence I can't add the relevant permissions to the blueprint and the Work IQ tools don't work in n8n anymore:

On top of this, I'm getting an error that:

Some actions may be disabled due to your permissions. To request access, contact the application owner(s) or your administrator. View application owners or administrators.

BUT I AM the application owner AND a global administrator on the tenant. So I can't even change permissions via the UI...

Expected behavior

No response

SDK Version

n/a

Language/Runtime

n8n

OS

macOS

How to Reproduce

Follow the new guide with the CLI. Basically the steps are:

1. Run a365 setup requirements (see docs)
2. Run a365 setup all --aiteammate --agent-name (see docs)
3. Then finally a365 publish which creates the manifest.zip
4. Sideload that into admin.microsoft.com
5. Set notification URL via Tools > Agent Blueprint in Teams Dev center (from n8n workflow with the Agent 365 Trigger); make sure you've configured the credential correctly and activated the workflow, so the URL is reachable
6. Create Agent instance (now happens via m365 agentstore)

When you try after step 2 to create tooling manifest, you will run into issue 412, if you work around that by creating an empty file with just { } as contents and then populating the tooling manifest, then running a365 setup permissions mcp in theory this should add the permissions to the blueprint, but it fails due to the max number of inheritable permissions.

Output

No response

Screenshots

No response

Code of Conduct

• I agree to follow the Microsoft Open Source Code of Conduct.