Microsoft Entra Application Reference

This article summarizes the application registration models, authentication settings, redirect URIs, API permissions, and scopes used by MyQ integrations with Microsoft services.

Use this reference when:

• registering an application manually

• reviewing an automatically configured enterprise application

• planning whether integrations can share an application registration

• troubleshooting permissions, authentication, or consent

For the recommended automatic workflow, see Automatic App Registration.

Registration Models

Some integrations can be configured automatically from MyQ. Other integrations require a manual application registration in Microsoft Entra ID.

For Microsoft Entra ID, OneDrive for Business, and SharePoint Online, manual setup can use one shared application registration or separate application registrations for each integration.

Do not use a shared application with Microsoft Exchange Online or Universal Print.

A manually registered application can be shared by Microsoft Entra ID, OneDrive for Business, and SharePoint Online, provided it contains all settings and permissions required by the enabled integrations.

Do not share this application registration with Exchange Online or Universal Print. These integrations require dedicated registrations with different authentication configurations.

Application Registration and Service Principal

A manually registered application is represented in two places in the Microsoft Entra admin center:

• App registrations contains the application definition, including its identifiers, authentication settings, credentials, redirect URIs, and requested API permissions.

• Enterprise applications contains the service principal representing the application in the customer’s tenant. Access, consent, and tenant-specific permissions are managed here.

Automatic setup creates and configures the service principal used by MyQ.

Information Required by MyQ

For a manually configured integration, obtain the following information from the application’s Overview page:

• Application (client) ID

• Directory (tenant) ID

• Client secret, when required

Redirect URIs

For Microsoft Entra ID, OneDrive for Business, and SharePoint Online, manual setup can use one shared application registration or separate application registrations for each integration.

Microsoft Exchange Online and Universal Print use different application configurations and should not use the shared manual registration procedure for Microsoft Entra ID, OneDrive for Business, and SharePoint Online.

Replace:

• {hostname:port} with the hostname and HTTPS port of the MyQ server.

• {Application-client-ID} with the Application client ID of the application registration.

Connecting to the Application from MyQ

If you use automatic registration, MyQ gets the client and tenant information silently.

If you configure any integration manually, get these details from your application registration Overview page:

• Application (client) ID

• Directory (tenant)

• Client secret (Entra ID, OneDrive for Business and SharePoint Online)

Permissions Used During Automatic Setup

The permissions used to create and configure the application are separate from the permissions that the resulting application uses at runtime.

Runtime Permissions

Microsoft Entra ID Permissions

OneDrive Permissions

SharePoint Permissions

Microsoft Exchange Online Permissions

Microsoft Universal Print Permissions

Authentication Scopes

Entra ID / Microsoft Graph

Authentication scopes are used during OAuth or OpenID Connect authentication.

Exchange Online

Universal Print