In this post I will demonstrate how to migrate the Microsoft Company Communicator between Azure subscriptions.
Company Communicator is a custom Teams app that enables corporate teams to create and send messages intended for multiple teams or large number of employees over chat allowing organization to reach employees right where they collaborate. Use CC for multiple scenarios, such as new initiative announcements, employee onboarding, modern learning and development, or organization-wide broadcasts.
The app provides an easy interface for designated users to create, preview, collaborate and send messages. It's also a foundation for building custom targeted communication capabilities, such as custom telemetry on how many users acknowledged or interacted with a message.
The official version is available at OfficeDev/microsoft-teams-apps-company-communicator, but in case you want to use extra features like tracking who interacted with your messages (reading, buttons clicked, reactions sent) or using a CSV file to send messages, my suggestion is to use the Cristiano's fork.
You can find more details about the Cristiano's version here.
It is possible to migrate 99% of CC automatically on Azure Portal except by the "Front Door and CDN profiles" one, that requires you do manually create the resource on the destination subscription.
Before starting, make sure that your destination Azure subscription has permission to create the following kinds of resources:
This step will check whether these resources can be moved, and this might take a few minutes.
In case you forgot to remove the Front Door and CDN profiles, during the validation, you will receive an error saying that the CDN couldn’t be migrated as it is not supported migrating resource types of 'Microsoft.Network/frontdoors.
If this is your case, remove the Front Door and CDN profiles item from the list. We will manually create it later from scratch in the target subscription. Click on Next again to start over the migration validation.
After a few minutes, it will remain only the Front Door and CDN profiles in the original resource group:
As next step, we need to manually create the Front Door and CDN profiles. Copy all information from your front door and then delete it before proceeding as we want to use the same values.
In case you receive the following error message:
In order to create this CDN profile, please ensure that Microsoft.CDN is listed as a registered Resource Provider in your Azure subscription.
Switch back to the Azure Portal home, click on Subscriptions, select the target subscription, click on Resource Providers, search for Microsoft.CDN, click on the result item and click on Register:
Once registered, switch back to the step 8 to start over the Front Door and CDN profiles creation.
Done! I hope it helps you!
ヾ(⌐■_■)ノ♪
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.