TEOC v3.4

• New Feature: Dashboard restricts the visibility of the incidents as per the current user. A user can see only the incidents that they are part of.
• New Feature: Ability to add M365 groups under roles while creating an incident. However, the recommendation is to use M365 groups with not more than 200 users due to few limitations.
• New Feature: Ability to select additional planner buckets while creating tasks from Active Dashboard.
• New Feature: Ability to configure and create default tasks while creating the incident depending on the selected Incident Type
• Minor accessibility improvements

TEOC v3.3

New Feature: "Bings Maps" replaced with "Azure Maps" in "Map Viewer" component. Since Bing Maps is deprecated, even customers who already had Bing Maps configured in TEOC need to replace it with Azure Maps as per "Enable Map Viewer" section in the "Solution Overview" wiki.

TEOC v3.2

• New Feature: Ability to configure "Edit Access Role" under "Admin Settings -> Config Settings" which provides a selected role the ability to edit incidents apart from "Incident Commander" and "Secondary Incident Commander"

• Bug fix: Gaps in the dropdown lists when creating an incident fixed

• Bug fix: Modified PowerShell script for SharePoint site provisioning to accommodate the changes made to PNP Management Shell registration in Microsoft 365

• Minor accessibility improvements

TEOC v3.1

• Upgraded Teams JS to version 2.21.0
• Accessibility improvements
• Bug fix: Update incident fails when same user is assigned as a team member and lead for 'Secondary Incident Commander' role.

TEOC v3.0

• New Feature: Accessibility compliant UI
• New Feature: Map Viewer on dashboard for Incidents
• New Feature: Ability for the admins to enable/disable map viewer and provide Bing maps key
• New Feature: Location picker while creating incidents
• New Feature: Incident Manager names in dash board replaced by person cards
• New Feature: Sorting implemented for all columns in dashboard table
• New Feature: Export to PDF functionality for Incident History
• New Feature: Dashboard tab created automatically in 'General' channel in the teams created for an incident
• New Feature: Ability to create 'Private' channels while creating incidents
• New Feature: Adaptive cards sent to Incident teams when a bridge is enabled/disabled through 'Active Dashboard'
• New Feature: Admins can modify the App Title
• Migration of classic Application Insights to workspace-based Application Insights.

TEOC v2.0

• New Feature: Supported in GCC High environment.
• New Feature: Active Dashboard - View Role Assignments and Leads, Post Channel Announcements, Create and Join Bridge, Create and Manage Planner Tasks.
• New Feature: Ability to assign Role Lead for each role.
• New Feature: Ability to enable Role based access to control access to "Manage Settings" and "Create New Incident" features.
• New Feature: Ability to add Guest Users from the incident and assign them to any role except Secondary Incident Commander.
• New Feature: Ability to add Cloud Storage Location on the incident.
• New Feature: Ability to Create or Modify Team Channels during incident creation.
• Enhancement: Add Secondary Incident Commander as owners to the team.
• Bug Fix: Create incident fails in the tenant where the site creation path was set to /teams/ in SharePoint Admin Portal.

TEOC v1.0

• New Feature: Ability to configure the Team Name format from dashboard.
• New Feature: Ability to view the version history for each incident from dashboard.
• New Feature: Ability to "Save default users for Roles" and "Save default roles for an Incident Type".
• New Feature: Local language support (translations) available for 12 languages.
• Upgraded the Teams toolkit version from v3.7.0 to v4.0.5

TEOC v0.5.1

• Allow users to manage roles and incident types from dashboard.
• Fix for incident creation failure for GCC tenant.
• Wiki updates

TEOC v0.5

• Allow users to create incidents based on the type of incidents and location.
• View and manage the incidents from the dashboard.
• Allow users to work in dedicated Teams channels for each incident.
• Allow users to manage the data in their SharePoint tenant.