Back to Company Communicator – New features and Bug fixes

Happy new year everyone. I found some time to work on a few Company Communicator bug fixes and a special new feature that is being requested for those ones using the dev build.

I have the pleasure to announce that the Company Communicator targeting mode is now available on my unofficial CC master branch. You can get more information, including instructions on how to enable and use the feature here.

The master branch is now complete with the targeting mode, analytics and also updated with version 4.1.5 codebase. I know the main code is now on v5 but I promise I’ll start the work on that soon. 🙂

This new release has the following additions:

  • New feature: Targeting Mode (as mentioned). That mode implements a two layer administration approach for CC. The master admin can install multiple instances of the authors interface in different Teams channels, and for each channel there will be a separate set of messages. That is, messages created by the Human Resources team will be only available for authors in that group and will not be available for authors of the Sales department, for example. The same admin also defines M365 security groups that will be available as the only options to send messages. There are also specific branding customizations that can be done per channel. You basically get a multi department communication tool, with limited governance just deploying one instance of Company Communicator.
  • Improvement: We now show the current size of the card and the maximum size so authors can manage to get the content under the limit of the Azure table record. That is a major thing for authors. Azure tables have a limit of 32K per record and CC uses that low cost database technology. When creating or editing messages authors can now see the space that is currently available so they don’t have any chances to create messages that are bigger than the limit (please note that I’m restricting in 30K just to be safe).
  • Improvement: This version also allows the upload of CSV files with a list of UPNs identifying users that will receive messages. The authors interface is now checking the size of the uploaded CSV file and comparing to the remaining space we have on the card. If the file is bigger a message is shown to the user. We are storing the CSV file in the same record used by the message thus subject to the 32Kb limit. This is something I’m looking into and I promise I’ll use a different approach in the future to avoid the 32K limitation, at least for the CSV user list.

  • Bug fix: Clicking to upload a new file is now resetting the size of the card. Previously, authors had to type a space or anything on the text field to clean up the image buffer. Now when you try to upload a new file it automatically clears the buffer.

  • Bug fix: Show the targeting channel customization during send visualization. I got a few customers complaining that when sending the messages the branding was not being shown. This version now has all the fixes to allow the correct visualization, including the branding.

As I said before, this is a side project I have to improve CC with some features requested by our customers in a unofficial way. If you want to use this variant/fork, remember that there is no official support provided by Microsoft.

If you have any questions, suggestions or complaints, please use the comments section here or create an issue on the GitHub repository.

Stay safe, Cristiano.

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.

12 thoughts on “Back to Company Communicator – New features and Bug fixes

Add yours

  1. Hi Cristiano,

    I’m using the CC app and sending the messages from the mobile device. When I get the notifications for the message and read the message from the device the read status and count does not track the message. Is that the default behavior ? Can’t we track the read from the mobile device ?


  2. I’m not able to track the reads from the mobile device once the message has been send. Tracking works well within the teams app when we read the message. Is that the default behavior ? Can’t we track the read from the mobile device ?


      1. May be I’m using older version of the code. Which version should I use to make this work on the Mobile device.


      2. I’m still not able to make this work on mobile device for read status. I’m using version 4.1.5. Any feedback will be much appreciated.


      3. As I said. I tested again (just a few seconds ago) and the reading on my iPhone is reflecting on the counter. Give a bit more details about your test environment. Are you using android or iphone? Do you have any firewall or peoxy blocking access to the azure app service? Can you post a screenshot of your Deployment Center sync configuration? What is the github URL you are using as the sync source? Have you disabled read tracking in the configuration?


    1. Hi Fabio, on the upper right corner you will see a counter that shows the size of your card against the maximum limit of ~30K. You CSV file + the whole card cannot go over 30K. That is because we load the CSV content to the same record we use to store the card, and that record has that limit with the database technology we are using. I know we should be uploading the file to the blob storage and then processing it, but that was just the easiest way to do. I recommend use the CSV file just when you’re sending messages to a small number of users. If you have a big list, please create a group and use that as the target for your audience.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Website Powered by

Up ↑

%d bloggers like this: