# Configuring Access To Microsoft Teams Organization administrators are able to set up Cronofy to automatically provision Microsoft Teams as a conferencing option for their users. However, unlike with our other Microsoft Enterprise features, Microsoft require extra permissions to be granted in order for Cronofy to create meetings on behalf of users in your Office 365 tenant. This is not required if you are using a full Read-Write calendar connection with Microsoft Teams enabled. This requirement is referenced in the permissions section of [Microsoft's API documentation for the create onlineMeeting endpoint](https://learn.microsoft.com/en-us/graph/api/application-post-onlinemeetings?view=graph-rest-1.0&tabs=http#permissions) ### Configuring an ApplicationAccessPolicy To configure an application access policy and grant Cronofy the ability to create meetings: - Start up PowerShell ``` pwsh```
    - Connect to Microsoft Teams PowerShell ``` Connect-MicrosoftTeams``` You may need to first install the `MicrosoftTeams` module. You can learn more about [Managing Teams in Powershell](https://learn.microsoft.com/en-us/microsoftteams/teams-powershell-managing-teams): ``` Install-Module -Name MicrosoftTeams```
      - Check you are connecting to the official Cronofy application. The ID for Cronofy Enterprise for Teams is: `bae01f9c-3537-4b0d-97c4-30d4a6f2c972`. If you wish to verify this, you may do so as follows:

      - If you have already authorized your connection, you may confirm this by visiting the [Azure Active Directory Enterprise application portal](https://portal.azure.com/#blade/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/AllApps/menuId/) as seen below. ![](/calendar-admins/enterprise-connect-microsoft-teams/enterprise-connect-access-id.309dad4a0cba48bcb1700f985d4dcb2bc9819b7aaa1a68db9ad87668234a5507.png) - If you have not yet authorized the connection, you can see the application ID visible in the address bar when initiating (but without completing) the connection: ![](/calendar-admins/enterprise-connect-microsoft-teams/auth-flow-client-id.2667acdb1fe0f748e06f71ab524fa79847530483b3fb9ce47f0eeac1482fcc19.png) - Should you want to verify that no existing policy exists, you can list all policies with the following command: ``` Get-CsApplicationAccessPolicy```
      1. Create an Application Access Policy with the Cronofy Enterprise for Teams Application ID. ``` New-CsApplicationAccessPolicy -Identity "CronofyMsTeamsEC" -AppIds "bae01f9c-3537-4b0d-97c4-30d4a6f2c972"```
        - `-Identity` value can be any string you like if you wish to alter this to something more useful for your tenant, "CronofyMsTeamsEC" is just for example. - `-AppIds` needs to point to "bae01f9c-3537-4b0d-97c4-30d4a6f2c972".
          - Now you need grant this new Application Access Policy to the users in your tenant. This can be done individually for testing, or you can use the `-Global` parameter to apply to all users within the tenant. Refer to [Microsoft's documentation](https://learn.microsoft.com/en-us/graph/cloud-communication-online-meeting-application-access-policy) for a more comprehensive guide on configuring Application Access Policies. ``` Grant-CsApplicationAccessPolicy -PolicyName "CronofyMsTeamsEC" -Global```
            - Finally you can verify the new Application Access Policy exists by calling ``` Get-CsApplicationAccessPolicy```

            Note: Changes to application access policies can take up to 30 minutes to take effect, based on Microsoft's documentation. #### Additional reading For further reading on the mechanism mentioned in this article, please see [this documentation from Microsoft](https://learn.microsoft.com/en-us/graph/cloud-communication-online-meeting-application-access-policy). If you require any further assistance, please contact us at [support@cronofy.com](mailto:support@cronofy.com). --- [Read in HTML](/calendar-admins/enterprise-connect-microsoft-teams/)