Hi Hamin Han ,
Thank you for your inquiry regarding the integration of a custom Copilot Studio agent within an Outlook add-in for internal use. Please find below the clarifications based on Microsoft’s current licensing and deployment model:
User Licensing Requirements: Users interacting with the Copilot Studio agent indirectly via the Outlook add-in are not required to have individual Copilot Studio licenses. This is because the interaction occurs through a backend service (the add-in), not the Copilot Studio UI. The agent functions like a customer-facing chatbot, where end-user licenses are not necessary.
However, if users do not have Microsoft 365 Copilot licenses, message-based billing will apply under the Copilot Studio consumption model.
Billing Model: Copilot Studio provides two options for billing message consumption:
Message Packs: Prepaid 25,000 messages per tenant/month at $200/month.
**Pay-as-you-go (PAYG)**: $0.01 per message sent/received.
These charges apply to all user interactions without Microsoft 365 Copilot licenses, even when accessed indirectly through the add-in.
**Deployment and Integration:** Your planned approach using **Node.js**, **Yeoman**, and **Office.js** for building the Outlook add-in is supported. The add-in can securely pass email content to the Copilot Studio agent via API and return the processed response.
Key requirements:
Ensure the agent is published and accessible via a secure endpoint.
Confirm that Copilot Studio metering is enabled in the **Power Platform Admin Center** to track and manage usage.
**Summary:**
Aspect | Requirement/Status |
---|---|
Direct user license | Not required for indirect add-in access |
Direct user license | Not required for indirect add-in access |
Microsoft 365 Copilot | Optional; reduces billing if available |
Billing model | Message-based (Message Packs or PAYG) |
Agent authoring | Requires Copilot Studio author license |
Deployment | Supported via Microsoft 365 Admin Center |
Thanks,
Karan Shewale
*************************************************************************
If the response is helpful, please click "Accept Answer" and upvote it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.