This repository documents the manual creation of an Azure Immersive Reader resource in the Azure portal and configure Azure Active Directory authentication.
The Azure Immersive Reader is a helpful resource that allows you to embed an accessible text reader with features like reading aloud, translating languages, focusing attention through highlighting, etc. More documentation can be found here.
Creating the Azure Immersive Reader requires the configuration of Azure Active Directory permissions. This is because the Immersive Reader only works with Azure AD permissions (it does not support authentication with connection strings, managed identities, or access tokens).
The steps to create the Immersive Reader resource and configure the Azure AD authentication are documented on the Microsoft Docs. However, I encountered issues when running the PowerShell script due to breaking changes in the APIs. Therefore, I researched how to create the Immersive Reader resources manually through the Azure Portal and am documenting it here to help make it easier to create the resources.
- An Azure account with the necessary permissions as documented here https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal
- A resource group in which you will create the resources
-
In the Azure Portal, create a
Immersive Reader
resource by searching for Immersive Reader.
-
Navigate to
Azure Active Directory
by searching forAzure Active Directory
. -
Take note of the Application (client) ID and the Directory (tenant) ID (hidden here for security purposes)
-
Navigate to
Certificates & secrets
witin the app registration -
Note the secret value (you can only copy it upon creation, so store it well)
-
Return to the Immersive Reader resource and note the subdomain of your endpoint
-
Go to the
Access control (IAM)
of the Immersive Reader resource -
Assign access to the Azure AD app registration you created previously
-
Review & assign
-
You may now use the Immersive Reader resources as documented in the quickstart guides. You have taken note of the tenant id (in step 5), the client id (in step 5), the client secret (in step 8), the subdomain (in step 9). You will need these to use the Immersive Reader SDK.