Skip to content

Guided tour

FabrCore 2.0 · Release and package availability

These guides track the current 2.0 source. Stable 2.0.0 publication is pending; package commands show the release target. Until it is published, follow the source quick start or use a matching available prerelease set. Release migration · Runtime modes

MODULE 10 · LESSON 10.1

Choose the Microsoft integration path

Choose the Microsoft integration by the direction of the call.

Lesson 53 of 86 · FabrCore 2.0

Overview

People chatting in Teams/Copilot use the activity-protocol addon. Copilot Studio calling FabrCore uses inbound A2A. FabrCore calling Graph or MCP uses connections. FabrCore calling Studio/Work IQ uses outbound remote agents. Each has its own authentication and lifecycle.

Start with who calls whom

A user chatting in Teams or Microsoft 365 Copilot reaches the activity-protocol addon. Copilot Studio orchestrating FabrCore uses inbound A2A. A FabrCore tool reading Microsoft Graph uses a connection. A FabrCore agent asking Studio or Work IQ for reasoning uses an outbound remote-agent integration. All can coexist, but installing one does not enable the others.

Choose by the direction of the call
Component / choice What it owns What it does not do
Person in Teams/Copilot → FabrCore Activity-protocol addon and /api/messages Use inbound A2A as its ordinary channel-chat transport
Copilot Studio → FabrCore Inbound authenticated A2A agent/task interface Install the Teams activity addon for you
FabrCore → Microsoft resource Protected connection plus Graph/MCP business tool Grant consent from an operator’s profile edit
FabrCore → Studio/Work IQ agent Outbound provider/remote-agent binding Share remote conversation state across unrelated users

Each boundary has its own identity

Application sign-in identifies the user to your product. Delegated consent authorizes a downstream resource. The cloud operator manages environments. A workload credential identifies a service. Write these identities beside the arrows in your diagram before configuring an app registration; using the wrong token audience can make otherwise correct code fail.

Choose the direction of integration

  1. Draw the direction of the first integration you need. Keep Azure OpenAI model configuration separate from Microsoft user identity.
  2. Choose a test tenant/app registration and identify the user, app or agent identity that will call each endpoint.
  3. Complete one direction end-to-end before combining it with the next. Keep the existing local fixture path available for comparison.

Draw one integration before configuring it

  1. Choose one concrete feature, such as “The Operations Desk web user reads their calendar.” Draw user → your app → FabrCore plugin → Graph and mark which call needs delegated consent.
  2. For “A Teams user chats with the assistant,” draw the activity endpoint path instead. Do not reuse the Graph plugin path as the inbound chat integration.
  3. List the client, Host addon/broker, Microsoft registration and live tenant prerequisites for your chosen path. Continue only with the lessons that implement that direction.

The output is an integration map with a clear caller, destination and identity at each hop. There is no Microsoft-wide switch that substitutes for this choice.

If the result is different

Inbound A2A success does not establish outbound Work IQ or Studio authentication. A Copilot channel registration is not a Graph connection grant.

Go deeper

Explore the related documentation.