This week we have an awesome contribution from Mike Francis and Luis Henrique Demetrio, two CEs from our App Consult team. They jumped to the challenge to extend the tracking framework we created for Company Communicator a few months ago to also track button clicks.

This is a change requested by multiple customers and is now active on the master branch for the community fork available at

Message Authors will see a summary of button clicks on the message status page. Clicks per user are also tracked and available via Power BI. Users will not see any change in the behavior of the app, the feature is additional to everything already incorporated so far.

See the screenshot below of the updated Message Status page. Note the new ‘Button Clicks’ section.  This shows a summary of the total number button clicks for all recipients of the message. In this case, the message was sent to 17 people, read by one. The ‘PowerPoint’ button was clicked once.

Notifications tab for the PBIX (Insights) report was also changed to incorporate data about the clicks.

Ah. Note that the report now has user names. That was implemented using a CSV dump from Azure Active Directory to the PBIX model. Easy solution!

As usual, if you already have the Community Fork you just need to resync the App Service and all Azure Functions. Here are the steps if you need:

Note: If you are using v5 (Official Version) those features will not work and you cannot update directly from the community fork. You need to follow steps required to update your version. Please check this article with further information.

  1. Open your Azure Portal and authenticate using admin credentials.
  2. Open the resource group where you installed Company Communicator.
  3. Select the App Service being used by CC and click on Deployment Center, under Deployment.
  4. In Settings, click Disconnect under External Git.
  1. Click OK to disconnect your deployment.
  2. Under Source, select External Git.
  1. In Repository, type
  2. In Branch, type master
  3. Leave the Repository Type as Public, and click Save.
  4. Click Sync.
  5. The whole update process will take a few minutes. Make sure you see Success (Active) on the logs tab.
  6. Now repeat that for each one of the Azure Functions you have on the same resource group. Those are the resources listed as:
    • <ccname>-data-function
    • <ccname>-function
    • <ccname>-prep-function

Disclaimer – The information contained in this blog post doesn’t represent the official Microsoft guidance or best practices. It is just the view of the author on current alternatives, implementations and workarounds for common issues and/or business needs. Please refer to official Microsoft documentation and evaluate carefully any steps, code or procedures documented herein. The author doesn’t offer any warranty. Use this information at your own risk.