page_type | description | products | languages | extensions | urlFragment | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
sample |
This sample application showcases how to post notifications in Microsoft Teams when users create, edit, or delete teams and channels using Microsoft Graph and C#. |
|
|
|
officedev-microsoft-teams-samples-graph-change-notification-team-channel |
This sample application illustrates how to implement team and channel subscriptions in Microsoft Teams, enabling real-time notifications for user actions such as creating, editing, or deleting teams and channels. Built using C# and the Microsoft Graph API, it provides detailed setup instructions, including Azure AD registration, bot configuration, and certificate management, making it easy for developers to create interactive and responsive applications.
- Tabs
- Graph API
- RSC Permissions
- Change Notifications
- Microsoft Teams is installed and you have an account (not a guest account)
- .NET 6.0 SDK.
# determine dotnet version dotnet --version
- dev tunnel or ngrok latest version or equivalent tunneling solution
- M365 developer account or access to a Teams account with the appropriate permissions to install an app.
Note these instructions are for running the sample on your local machine.
-
Run ngrok - point to port 3978
ngrok http 3978 --host-header="localhost:3978"
Alternatively, you can also use the
dev tunnels
. Please follow Create and host a dev tunnel and host the tunnel with anonymous user access command as shown below:devtunnel host -p 3978 --allow-anonymous
-
Setup for Bot
- Register a new application in the [Microsoft Entra ID App Registrations portal.
- On the overview page, copy and save the Application (client) ID, Directory (tenant) ID. You'll need those later when updating your Teams application manifest and in the appsettings.json.
- Navigate to API Permissions, and make sure to add the follow permissions:
-
Select Add a permission
-
Select Microsoft Graph -> Application permissions.
-
Channel.ReadBasic.All
,ChannelSettings.Read.All
,Directory.ReadWrite.All
,Group.ReadWrite.All
Team.ReadBasic.All
,TeamSettings.Read.All
,TeamSettings.ReadWrite.All
-
Click on Add permissions. Please make sure to grant the admin consent for the required permissions.
- Navigate to the Certificates & secrets. In the Client secrets section, click on "+ New client secret". Add a description (Name of the secret) for the secret and select Expiry date. Click "Add", Once the client secret is created, copy its value because it needs to be placed in the appsettings.json file.
In Azure portal, create a Azure Bot resource.
- Ensure that you've enabled the Teams Channel.
- In Settings/Configuration/Messaging endpoint, enter the current
https
URL you were given by running the tunnelling application. Append with the path/api/messages
To include resource data of graph notifications, this Graph API require self-signed certificate. Follow the below steps to create and manage certificate.
-
You can self-sign the certificate, since Microsoft Graph does not verify the certificate issuer, and uses the public key for only encryption.
-
Use Azure Key Vault as the solution to create, rotate, and securely manage certificates. Make sure the keys satisfy the following criteria:
- The key must be of type
RSA
- The key size must be between 2048 and 4096 bits
- The key must be of type
-
Follow this documentation for the steps - Create and install Self-Signed certificate
-
Clone the repository
git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git
A) If you are using Visual Studio
- Launch Visual Studio
- File -> Open Folder
- Navigate to
samples/graph-change-notification-team-channel/csharp
folder - Select
ChangeNotiifcation
solution file
Instruction for appsetting 1. Provide MicrosoftAppId, MicrosoftAppPassword and MicrosoftAppTenantId in the appsetting that is created in Azure. (Note the App Password is referred to as the "client secret" in the azure portal and you can always create a new client secret anytime.) 2. Provide the tunnel url as "BaseUrl" in appsetting on which application is running on. 3. You should be having Base64EncodedCertificate and CertificateThumbprint value from Create and install Self-Signed certificate step.
- Run your bot, either from Visual Studio with
F5
or usingdotnet run
in the appropriate folder.
B) This step is specific to Teams.
-
Edit the
manifest.json
contained in theAppManifest
folder to replace your Microsoft App Id (that was created when you registered your bot earlier) everywhere you see the place holder string<<YOUR-MICROSOFT-APP-ID>>
(depending on the scenario the Microsoft App Id may occur multiple times in themanifest.json
) -
Edit the
manifest.json
forvalidDomains
with base Url domain. E.g. if you are using ngrok it would behttps://1234.ngrok-free.app
then your domain-name will be1234.ngrok-free.app
and if you are using dev tunnels then your domain will be like:12345.devtunnels.ms
. -
Zip up the contents of the
AppManifest
folder to create amanifest.zip
(Make sure that zip file does not contains any subfolder otherwise you will get error while uploading your .zip package) -
Upload the
manifest.zip
to Teams (In Teams Apps/Manage your apps click "Upload an app". Browse to and Open the .zip file. At the next dialog, click the Add button.) -
Add the app to personal/team/groupChat scope (Supported scopes)
Note: If you are facing any issue in your app, please uncomment this line and put your debugger for local debug.
You can interact with Teams Tab by subscribing the teams/channel for notifications.
-
Show Welcome - Channel -> Welcome Message when Channel selected for subscription.
-
Channel Notifications -> Channel Created Update Delete Message
-
Show Welcome - Team -> Welcome Message when Team selected for subscription.