Skip to content
This repository has been archived by the owner on Feb 15, 2024. It is now read-only.

OfficeDev/Incident-Management-Teams-Provisioning

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

24 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Introduction

Organizations of all types need to respond to events and incidents, planned and unplanned. Responding in a standard and timely manner helps organizations achieve better outcomes and communications status to stakeholders.

Planning for events includes templated documents, communication processes, reporting dashboards and task management. Today organizations may have all those documents and tools in separate portals and platforms. Microsoft Teams is a central hub for collaboration and brings together these documents and sites into one work area.

With Microsoft Graph an event-specific Teams space is quickly provisioned by adding apps and populating templated documents from SharePoint libraries, insuring the event or incident is structured for execution and retention after it’s complete.

This project demonstrates how to provision Microsoft Teams with pre-configured channels, naming convention, templated documents, tab apps using Graph APIs, where all of the content management is configured in SharePoint lists. This project works across all types of Office 365 tenants, including Office 365 US Government Community (GCC).

noaa national weather map

Getting Started

  1. Install Visual Studio 2017 or 2019
  2. M365 Tenant admin account

We have published the following walk-through video to help with the deployment process and to get a functional understanding:

Build and Test

Configure the solution, build and test it on Windows platform

Contributing

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.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., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repositories using our CLA.

Microsoft Open Source Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct.

Resources:

About

Incident Management Teams Provisioning

Resources

License

Code of conduct

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •  

Languages