Description
I previously reported an issue with blueprint registration in #403, where I was completely unable to create a blueprint.
While that specific issue seems resolved — I can now successfully create a blueprint using the a365 setup all --aiteammate --agent-name <name> command — the new registration flow introduces two major blocking issues regarding Azure permissions and agent communication.
Actual Behavior
- Azure Portal Permission Issue
Right after creating the blueprint via the CLI, I navigate to this blueprint in the Azure Portal. However, I am greeted with the following warning:
Some actions may be disabled due to your permissions. To request access, contact the application owner(s) or your administrator.
This happens despite the fact that I just created it and I am a Global Admin. As a result, I am completely locked out of modifying this blueprint from the Azure Portal level.
- Teams Agent Communication Failure
If I proceed to create a manifest based on this blueprint and add it to my domain, the instance creation seems to work on the surface:
I click Create instance in Teams.
A green success message appears indicating the instance was created.
However, when I try to interact with the newly created agent instance (e.g., sending a message in Teams), no messages are sent to our application. I have checked our application logs, and there is absolutely no incoming traffic from the agent.
Expected behavior
-
As the creator of the blueprint and a Global Admin, I should have full permissions to edit and manage the blueprint directly in the Azure Portal without seeing permission warnings.
-
Messages sent to the successfully created agent instance in Teams should reach the application and be visible in the application logs.
SDK Version
1.1.174+25970fb6e6
Language/Runtime
Node 24
OS
macOS 26
How to Reproduce
-
Run the command: a365 setup all --aiteammate --agent-name <name>
-
Go to the Azure portal, locate the newly created blueprint, and observe the permission warning preventing any modifications.
-
Generate a manifest based on this newly created blueprint.
-
Add the manifest to the tenant.
-
In Teams, click Create instance (wait for the green success message confirming creation).
-
Send a message to the agent via Teams.
-
Check the application logs — observe that no message payload reaches the application.
Output
When running the a365 setup all --aiteammate --agent-name <name> command in the terminal, the execution completes successfully without any errors. The terminal output indicates a full success, and the blueprint is indeed created in Azure, making the issues apparent only during subsequent usage and testing.
Screenshots
No response
Code of Conduct
Description
I previously reported an issue with blueprint registration in #403, where I was completely unable to create a blueprint.
While that specific issue seems resolved — I can now successfully create a blueprint using the
a365 setup all --aiteammate --agent-name <name>command — the new registration flow introduces two major blocking issues regarding Azure permissions and agent communication.Actual Behavior
Right after creating the blueprint via the CLI, I navigate to this blueprint in the Azure Portal. However, I am greeted with the following warning:
This happens despite the fact that I just created it and I am a Global Admin. As a result, I am completely locked out of modifying this blueprint from the Azure Portal level.
If I proceed to create a manifest based on this blueprint and add it to my domain, the instance creation seems to work on the surface:
I click Create instance in Teams.
A green success message appears indicating the instance was created.
However, when I try to interact with the newly created agent instance (e.g., sending a message in Teams), no messages are sent to our application. I have checked our application logs, and there is absolutely no incoming traffic from the agent.
Expected behavior
As the creator of the blueprint and a Global Admin, I should have full permissions to edit and manage the blueprint directly in the Azure Portal without seeing permission warnings.
Messages sent to the successfully created agent instance in Teams should reach the application and be visible in the application logs.
SDK Version
1.1.174+25970fb6e6
Language/Runtime
Node 24
OS
macOS 26
How to Reproduce
Run the command:
a365 setup all --aiteammate --agent-name <name>Go to the Azure portal, locate the newly created blueprint, and observe the permission warning preventing any modifications.
Generate a manifest based on this newly created blueprint.
Add the manifest to the tenant.
In Teams, click Create instance (wait for the green success message confirming creation).
Send a message to the agent via Teams.
Check the application logs — observe that no message payload reaches the application.
Output
When running the
a365 setup all --aiteammate --agent-name <name>command in the terminal, the execution completes successfully without any errors. The terminal output indicates a full success, and the blueprint is indeed created in Azure, making the issues apparent only during subsequent usage and testing.Screenshots
No response
Code of Conduct