Deploying the Teams Connector with Azure Cloud Shell

This article provides guidelines for deploying the Teams Connector with Azure Cloud Shell.

It does not cover creating the certificate for the CVI app — you will need to generate a self signed certificate.

In general you should continue to follow the main deployment guidelines as described in Installing and configuring the Teams Connector in Azure unless directed otherwise here.

Azure cloud shell is not officially supported, but the Teams Connector deployments should work with the modifications below.

PowerShell modules

Module versions

Before starting deployment via cloud shell it's necessary to:

  • Install all the required versions of modules as per First-time use.
  • Make sure you install modules for the correct version of Teams Connector.
  • You need to omit the -Scope parameter as you can't install module for all users when using Azure cloud shell, i.e. use the format:
    Install-Module -Name {module name} -RequiredVersion {required version} -AllowClobber -Force

Now uninstall all the other Az.Account module versions that are installed for your user:

Get-InstalledModule Az.Accounts -AllVersions | Where-Object Version -ne {required version} | Uninstall-Module -Force

Ignore errors like Uninstall-Package: Module 'Az.Accounts' is in currently in use or you don't have the required permissions. The error is referring to the Az.Account module that is installed by default.

Important! Open a new Azure cloud shell session after the modules have been installed.

Connect-AzAccount

The default Cloud Shell account is the Managed service that is logged in automatically. You should be able to use this account.

If you need to log in using a different account, note that only device authentication is supported and therefore you must use:
Connect-AzAccount -UseDeviceAuthentication

Uploading the Teams Connector application software files to Cloud Shell

Make sure to use "clouddrive" folder (https://learn.microsoft.com/en-us/azure/cloud-shell/persisting-shell-storage).

Click Manage files > Open file share and upload Teams Connector ZIP file.

The file will appear in the "clouddrive" folder.

You must use Expand-Archive to extract the files. Do not use unzip as this will cause a failure when deploying admin consent.

You must upload all the necessary certificates to the clouddrive.

Timeouts

The Cloud Shell has a default timeout of 20 minutes.

Note that each time you reconnect you need to rerun the variables initialization script.

Additional information

Any "Set-ExecutionPolicy: Operation is not supported on this platform" errors can be safely ignored.

Any "Unblock-File: The cmdlet does not support Linux" errors can be safely ignored.