Add-in deployment options
Choose one of the following installation options and connect the OIDC / SSO login:
​
User based installation via Microsoft's app store AppSource
If the Microsoft app store, AppSource, is available for users, people can easily install the add-in via this option.
​
Either, follow this link: Data Quality Assistant in Microsoft AppSource, or search in Excel directly, go to:
Insert > Get Add-ins > Search for "Data Quality Assistant" > Click "Add" and follow the instructions.

Admin managed installation options
We offer multiple options to roll-out the Data Quality Assistant to users in an organisation. If you want to know more about updating an existing installation, see here.
Admin Center: Integrated Apps
1. In the admin center, select Settings, then select Integrated apps.

2. Select Get apps at the top of the page. AppSource will load in an embedded format. Search for “Data Quality Assistant”. Select ”Get it now” or Deploy.

3. You will see the Configuration page where all the apps are listed. If you don’t have permissions or the right access to deploy the app, the respective information will be highlighted. You can select the apps you want to deploy. By selecting. Next, you will view the Users page.
4. Select Everyone, Specific users/groups, or Just me to specify whom the add-in is deployed to. Use the Search box to find specific users or groups.

5. Select Next. All the app capabilities and permissions are displayed in a single pane along with certification info if the app has Microsoft 365 certification. Selecting the certification logo lets the user see more details about the certification.
6. Review, and then select Finish deployment.
7. A green "tick" icon appears when the add-in is deployed. Follow the on-page instructions to test the add-in.

Admin Center: Custom App (upload / link manifest file)
-
In the admin center, select Settings, then select Integrated apps.
-
Select Upload custom apps at the top of the page. An Upload screen opens. Upload the manifest.xml which you can find at the bottom of the latest release notes.
-
You see an overview and users tab, click on Users and select the appropriate users in the next step.
-
Select Everyone, Specific users/groups, or Just me to specify whom the add-in is deployed to. Use the Search box to find specific users or groups.
-
Select Next.
-
Review, and then select Finish deployment.
-
A green "tick" icon appears when the add-in is deployed. Follow the on-page instructions to test the add-in.
​
-
Go to the Active sites page of the new SharePoint admin center and sign in with an account that has admin permissions for your organisation.
-
Open the app catalog site by selecting its URL in the URL column.
-
Choose Distribute apps for Office.
-
In the Apps for Office page, choose New.
-
In the Add a document dialog, select the Choose Files button.
-
Locate and specify the manifest.xml which you can find at the bottom of the latest release notes.
-
In the Add a document dialog, choose OK.
SharePoint app catalog
-
Create a folder named "DQA" either
-
... on a shared network drive
-
Mark and copy the network path (\\network_drive\...)
-
-
... or on your local PC
-
Right click on the "DQA" folder
-
Click: Properties > Tab "Sharing"
-
Mark and copy the network path (\\name_of_your_computer\...)
-
Click “Release” > and click “Release” again in the pop-up
-
Click “Done” in the pop-up and confirm
-
-
-
Save the manifest.xml file which you can find at the bottom of the latest release notes in the "DQA" folder, named "manifest.xml"
-
Open Excel > File > Options > Trust Center > Trust Center Settings
-
Trusted Add-in Catalogs > Catalog Url > right mouse click and paste the copied network path > "Add catalog"
-
Select Add-in and scroll to the far right and check “Show in Menu” > OK > OK.

Restart Excel
-
Click Insert > Get Add-ins > Shared Folder > Select Add-in and click “Add” and get started
(a restart can be required as well)
​
More information available in Microsoft's Sideload Office Add-ins documentation.
Configure single sign-on (SSO) and automated user provisioning
Microsoft Login
​
1. Visit the Azure AD App Gallery and click New, search for "Data Quality Assistant"

2. Click on "Data Quality Assistant" by Data Q Company GmbH
3. On the right pane menu, click "Sign up", user's from your organisation can easily use the Federated SSO connection and choose "Sign in with Microsoft" in the Add-in and on our platform
Okta Login
You can create an Okta OIDC app integration and send us the client credentials via a secure channel. We will integrate the client ID and secret.
​
-
Launch OIDC Okta Wizard: Admin Console: Applications > Create App Integration > Select OIDC - OpenID Connect as the Sign-in method
-
Select Web Application as type of application
-
Next
-
General Settings:
-
App integration name: "DQ Assistant by DQC"
-
(Optional) Logo dqc-okta-bannerlogo.png
-
Grant type: Client Credentials
-
Sign-in redirect URIs:
-
https://q.dqc.ai/auth/self-service/methods/oidc/callback/<Second-Level-Domain (SLD)>
-
Example for acme.org -> "acme" is the second-level domain (SLD) https://q.dqc.ai/auth/self-service/methods/oidc/callback/acme
-
-
(Optional) Sign-out redirect URIs: https://q.dqc.ai/auth/self-service/login/browser
-
-
Save > This creates the app integration and opens the settings page to configure more options.
Configure OIDC settings (from Okta documentation)
​
-
The Client Credentials section contains important information necessary for authentication flows.
-
Client ID: This identifier is randomly generated when you create the app integration.
-
Client authentication: Choose the method to use for client authentication.
-
Client secret: Selecting this option displays a panel where you can generate a secret for use by the client. This value is known only to Okta and your app integration. Click Save to generate the client secret. You can view and copy the client secret.
-
-
Click Save to commit any changes to your Client Credentials.
-
​
Put both client ID and secret into a file (e.g., text-file) and send it via a secure channel.
The following secure channels are recommended - PGP encrypted file as best practice:
​
-
PGP Encrypted file with the following PGP keys: Johannes Boyne (CTO) | Security @ DQC
-
Password protected ZIP with a password and two channels, e.g., e-mail and MS teams (or call)