page_type | languages | products | description | urlFragment | ||||
---|---|---|---|---|---|---|---|---|
sample |
|
|
Simple Azure Functions bot for managing incidents from Microsoft Teams |
functions-teams-incident-status-page-bot |
Outline the file contents of the repository. It helps users navigate the codebase, build configuration and any related assets.
File/folder | Description |
---|---|
src |
Sample source code. |
.gitignore |
Define what to ignore at commit time. |
CHANGELOG.md |
List of changes to the sample. |
CONTRIBUTING.md |
Guidelines for contributing to the sample. |
README.md |
This README file. |
LICENSE |
The license for the sample. |
- Azure Functions
- Azure SignalR Service
- Microsoft Teams
-
Create the Azure Function app, Storage account, and SignalR Service with this button:
-
Incident statuses are stored in a table in the Storage account, but there's no way to create this table with ARM. In the Azure portal, open the Storage account and add a table named
statuses
. -
Now navigate to the function app, and open the
teams-webhook
function. Click "Get Function URL" and copy the URL. -
Finally, open Teams and navigate to the "Apps" page of the team in which you want to create the bot. Click "Create outgoing webhook".
Use
StatusPage
as the bot name (this is hardcoded, for now). Paste in the function URL, and enter a description.You will be prompted with a secret code for validating webhook calls from Teams. We currently do not use this. Close the dialog box.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.