Company Communicator v4.1.4

• Support large number of users.
• Reduce memory usage in the prep function by dividing single orchestration into multiple sub-orchestrations and limiting the number of activity executions per sub-orchestration.
• Upgrade NPM packages.

Company Communicator v4.1.3

• Support users who have left the tenant in Export report functionality. With this change, authors can now download reports for messages which have recipients who have left the tenant.

Company Communicator v4.1.2

• Fix an issue that could result messages reaching guest users. With this fix:
  • Guest users with user app installed will not receive messages
  • The message recipient type i.e. Member or Guest can now be identified using export report functionality
• Fix bug that was preventing proactive installations
• Upgrade NPM packages

Company Communicator v4.1.1

• Fix an issue that could result in messages reaching guest users. This can happen when:
  • a message is sent to a team using the option to send to team members via chat, and the target team contains guest users, or
  • a message is sent to a group, and the group contains guest users, or
  • the Global app setup policy is used to install Company Communicator to all users. (The global setup policy now installs apps to guest users.)
• Fix bug with the author app interface in dark and high-contrast themes
• Resolve potential out of memory errors when sending messages to large numbers of users
• Upgrade NPM packages

See Excluding guest users from messages for steps to remove guest users from the existing users list.

Company Communicator v4.1

• Localized resource files for several locales
• Partial support for right-to-left languages. Note that RTL support in adaptive cards is still pending.
• Update NPM and Nuget dependencies

Company Communicator v4.0

• Split user and author functionality into different bots. With this change, the authors and users app packages now have different bot IDs, which enables you to use app permission policies to control access to the authors app. (In previous versions, using app permission policies with Company Communicator led to intermittent message delivery failures.)
• Include a Powershell script for deployment and upgrade from v3. The script checks for deployment prerequisites, creates and configures AAD applications, and deploys the resources to your Azure subscription. It can also detect and recover from some Azure deployment failures.
• Set isNotificationOnly to true in the app manifest. This was originally set to false to allow for recovery in case we missed the conversationUpdate activity, but now that we can get the chat thread ID via Graph, we can set this to true.
• Add unit tests for message send and preparation functions

Please see the wiki for upgrade instructions from Company Communicator v3.

Company Communicator v3.0.1

• Update ua-parser-js NPM package
• Update global.json to specify a minimum version of 3.1.108 (see .NET Core release notes)

Company Communicator v3.0

• Company Communicator can be configured to install itself to recipients who do not have the app already installed, so that CC can deliver the message to them. This is an optional feature that must be set during deployment, or later on in app service settings (ProactivelyInstallUserApp=true), and requires the TeamsAppInstallation.ReadWriteForUser.All Graph scope.
• Localizing the app is easier. We finished extracting user-facing strings into resource files. If translations are available, the CC user interface will follow the Teams language setting. (Note that the content of a message sent by CC remains in its original language.)
• Refactoring of the send pipeline, and various bug fixes.

Thank you to @cbitter78 and @garystewart247 for their contributions!

Solution overview: https://github.com/OfficeDev/microsoft-teams-company-communicator-app/wiki/Solution-overview
Migration guide from v2: https://github.com/OfficeDev/microsoft-teams-company-communicator-app/wiki/v3-migration-guide

Company Communicator v2.1.1

• Fix issue #196 (thanks to @sergiorru for the bug report and PR)
• Reduce the number of activity executions in the prep function by 50% by fetching user data sequentially instead of forcing a fanout for each user.

Company Communicator v2.0

• Enable targeting distribution lists and security groups (Note that the users in the list still need to have the app installed to actually receive the message. Users without the app will be reported as failed deliveries.)
• Export the results of sending a message
• Handle users who have left the tenant, so they are not reported as delivery errors