Teams Integration
NOTE: Workzone integrations like Teams are optional add-ons to Workzone. For details on adding this feature, if you don't have it already, please email help@workzone.com.
With Workzone's Teams integration, users can take advantage of Microsoft's communication platform to receive certain Workzone notifications within Team's Activity area (bell icon).
Supported Notifications
Currently, the following types of notifications from Workzone that are delivered via email messages are also supported for delivery via Teams:
- Downstream non-summary task responsible parties when non-summary predecessor tasks are marked as complete (created when using dependencies)
- Comments (including markup) to subscribed and/or @mentioned users
- New project request submissions
- Project request updates
- Approval requests recipients
- Approval request responses
NOTE: Teams notifications (once the integration is configured) are only delivered when the equivalent email notification is enabled within Workzone's settings.
Initial Configuration
Workzone's Teams integration can be set up in as little as 5-10 minutes.
NOTE: This process does require Microsoft Azure and Microsoft Teams administrator access
In Workzone, start in the settings (top right gear icon) for All Workspaces, on the Integrations page, under the Global section on the left.
Click the Teams block, shown here:
...and then click and follow each of the listed steps on that page, also described below:
NOTE: Some buttons or other actions on the Microsoft configuration pages described below may have a delayed response of several seconds or more, depending entirely on the performance of those pages by Microsoft.
Step 1:
Login to portal.azure.com and navigate to "Microsoft Entra ID".
Step 2:
On the left-hand side, under Manage click App registrations. On the page that appears, click + New registration.
Step 3:
On the registration page, enter a name for the app (“Workzone Notifications”, for example), leave the first radio button selected (“Accounts in this organizational directory only…”), and click Register at the bottom of the page.
Step 4:
On the page that appears, copy the Application (client) ID and Directory (tenant) ID values shown here:
...and paste them into the corresponding fields on the setup page in Workzone:
Step 5:
On that same App Registration page, to the right of the Application and Directory IDs, click the option to Add a certificate or secret.
On the page that appears, click + New client secret, enter a description for the client (“Triggering Notifications from Teams to Workzone” for example), and optionally choose how frequently the secret should expire. Click Add at the bottom of the page.
NOTE: Once a client secret expires, a new secret will need to be created in the Azure portal and updated in Workzone.
Step 6:
Once the new client secret has been added, it will appear on this page.
Copy the Value and paste it into this field on the setup page in Workzone:
Step 7:
Now that the client secret value has been entered into Workzone, click API permissions on the left-hand side, click + Add a permission, and then click Microsoft Graph.
Step 8:
On the page that appears, five permissions will need to be enabled. Copy & paste these permission names into the search field to locate the correct permissions and check the box next to each to enable the permission:
- TeamsActivity.Send
- TeamsAppInstallation.ReadWriteAndConsentSelfForUser.All
- User.Read.All
- User.ReadWrite.All
Once ALL permissions have been enabled, click Add permissions at the bottom of the page.
Step 9:
Now that the permissions have been added, they’ll be listed at the bottom of the page. Above the list of permissions, click Grant admin consent. In the pop-up that appears at the top of the page click Yes.
After a moment, the permissions will refresh and green checkmarks will appear next to each of the granted permissions.
Step 10:
Download the ZIP file by clicking the Download button on the setup page in Workzone.
NOTE: Mac/Safari users will need to uncheck the Open “safe” files after downloading setting, as described here, or locate and recover in their Mac's trash the original ZIP file downloaded.
Navigate to admin.teams.microsoft.com. On the left-hand side of the Microsoft Teams admin center page, click Manage apps under the Teams apps heading. On that page, click Actions ˅ in the top right and click + Upload new app in the menu that appears.
In the pop-up window that appears, click Upload, locate and select your recently downloaded ZIP file to upload it. Afterward what can take a moment, the overlay for uploading a new app can be closed.
Step 11:
On the left-hand side, click Setup policies under the Teams apps heading. On that page, click Global (Org-wide default).
Step 12:
On the page that appears, click Add apps in the middle of the page. In the pop-up window that appears enter “workzone” into the search field and click Select next to the Workzone app that appears.
NOTE: The new app may take a minute or two to appear in that menu. A page refresh may be required.
Once the Workzone app appears under the Apps to add section, click Add at the bottom of the page.
Step 13:
Once the app has been added, it will appear in the middle of this page. Confirm that it is listed and then click Save at the bottom of the page.
In the Changes will take time to take effect pop-up that appears, click Confirm. The app is now completely configured and users can begin receiving Workzone notifications in Microsoft Teams.
Editing An Existing Integration
After Workzone's Teams integration is all set up, it may be necessary to update the Client Secret or remove the integration altogether. This can be done by clicking the same Teams block mentioned at the beginning of the Initial Configuration section.
With the integration already configured, the page will display the IDs and Client Secret fields, as shown here:
Enter a new ID or Secret in the respective fields (clicking the small eye icon to the right will display the text currently entered in the field) and click the Save button to confirm the change, or use the Delete button to remove the Teams integration from Workzone altogether.
NOTE: Microsoft's configuration page(s) can still have entries and/or references to Workzone that may merit editing or removal.