Door Tablet and Microsoft 365 GCC High In this video We will show where to make the connection with Microsoft 365 GCC High We will discuss the limitation that is imposed by the platform and explain how this is overcome Door Tablet now works with Microsoft 365 GCC High This version of Microsoft caters to the needs of government organisations within the continental USA including the Department of Defense and other security agencies across North America Let's delve into the process of running Door Tablet in this environment The Door Tablet server must be installed, whether on-premise or on the cloud Now, let's explore how to connect to Microsoft 365 GCC High To begin, log into the system Open the System Profile It's crucial to note a limitation imposed by the platform, but it's easily overcome We'll discuss this shortly To make the connection to GCC High you will need to obtain the information to fill out this form You will need the Tenant ID, Application ID and Secret Value This is the same as what is required to make a connection to the global Microsoft 365 Watch our video ‘Connecting to Microsoft 365’ for instructions for how to get this information Once this is done, to make the connection to GCC High you will now select what type of end-point you are using Then we can initiate the test Upon pressing the button, Door Tablet signals its intent to use Microsoft GCC High Authentication takes place without attempting to check space status as this API call is restricted in this instance Moving forward, if we can't retrieve the list of resources, there's a workaround By submitting the request, we can manually create spaces Unlike the global version of Microsoft the synchronization button is unavailable due to API restrictions in the GCC High platform Creating spaces manually is a straightforward process Involving selecting a space, configuring checkboxes and entering the SMTP address of the desired room obtained from the Azure platform Despite the limitation on synchronisation all other Door Tablet functionalities remain unchanged compared to the standard version In summary, while the synchronisation process is a one-time task Door Tablet's core functionalities, including calendar access, reminders, and more remain fully accessible From an Azure perspective the app registration process remains identical to the standard one with the only difference being the ability to use one less scope specifically, the "Place.Read.All" scope Thank you for watching Door Tablet integrates room and workspace management with existing enterprise systems.