Setting Up the Teams Deployment
Teams deployments require an Azure AD (Entra ID) application that the agent uses to read messages and post replies. You can either connect via delegated OAuth (signing in as a user) or via an app-only service principal (recommended for production and DMs).1
Register an Azure application
Go to portal.azure.com → Microsoft Entra ID → App registrations → New registration. Give the app a name (e.g.
Noxus Agent) and register it.2
Grant Microsoft Graph permissions
Under API permissions, add the Microsoft Graph permissions the agent needs to read messages and post replies (for example
Chat.Create, ChatMessage.Read.All, Channel.ReadBasic.All, ChannelMessage.Send, Team.ReadBasic.All, User.Read.All). A tenant admin must Grant admin consent for the application-level permissions.3
Create a client secret
Under Certificates & secrets, create a new Client secret and copy the value — you will only see it once.
4
Enter credentials in Noxus
Back in Noxus, create a new Microsoft Teams connection and fill in the fields:
- Tenant ID — your Azure AD tenant UUID.
- Client ID (Application ID) — from the app’s Overview page.
- Client Secret — the value you copied in the previous step.
- User ID or Email (UPN) — optional. Leave empty for channel-only deployments; required when you want the agent to handle direct messages (DMs) with app-only permissions.
5
Install the Noxus app in Teams
Install the Noxus bot app into your Teams tenant (or add the bot to specific channels) so it can receive messages. The bot needs to be present in every channel where you want it to respond.
Deployment Settings
Once your Teams connection is established, configure how the agent behaves in Teams. Settings are organized into the sections below.Deployment
A published version is required before you can set a deployment to Online. You cannot edit the configuration while the deployment is active — switch it to Offline first, then make your changes.