--- title: "Setting up DocuWare for Outlook on-premises" slug: "install-docuware-for-outlook-on-premises" updated: 2026-07-01T13:26:25Z published: 2026-07-01T13:26:25Z canonical: "knowledgecenter.docuware.com/install-docuware-for-outlook-on-premises" --- > ## Documentation Index > Fetch the complete documentation index at: https://knowledgecenter.docuware.com/llms.txt > Use this file to discover all available pages before exploring further. # Setting up DocuWare for Outlook on-premises ocuWare for Outlook on-premises is an add-in that connects your local DocuWare installation with Microsoft Outlook. To enable this integration, you begin by registering and configuring the Microsoft Entra app, followed by a series of setup processes to establish a secure connection between DocuWare and Outlook. In sequence, configure the DocuWare server to conclude the preparation of your environment. Once these steps are accomplished, users can easily file emails and attachments directly to their on-premises DocuWare trays or file cabinets, streamlining document management within their organization. #### Prerequisites - A DocuWare Connect to Outlook license is required to access and use the add-in. - DocuWare setup was installed without any errors. - HTTPS Certificate is created and assigned to the website in IIS, so that the entire DocuWare is accessible via https://{{YOUR_DOMAIN}}/DocuWare Make sure the call to https://{{YOUR_DOMAIN}}/DocuWare/Outlook succeeds ![](https://cdn.document360.io/0108e24e-b3e8-446c-b670-66b1d2a9e861/Images/Documentation/image(585).png) #### Limitations - Storing emails from a shared mailbox is not supported in the desktop (classic) version of Microsoft Outlook. - The in-app feedback feature is unavailable, as DocuWare for Outlook on-premises cannot connect to DocuWare Cloud to submit feedback. ## Microsoft Entra OAuth app registration Begin by creating an OAuth app registration in Microsoft Entra at [Microsoft Entra App](https://entra.microsoft.com/#view/Microsoft_AAD_RegisteredApps/ApplicationsListBlade/quickStartType~/null/sourceType/Microsoft_AAD_IAM). For example: ![](https://cdn.document360.io/0108e24e-b3e8-446c-b670-66b1d2a9e861/Images/Documentation/image(604).png) Now the app is created. In the next steps, you will configure the app. > [!NOTE] > Ensuring correct SSO URL casing > > DocuWare for Outlook, use the exact casing configured during setup. Any uppercase or lowercase mismatch can cause SSO sign-in to fail. ### 1. Exposing an API First, open **Expose an API** to add a new application ID URI here. ![](https://cdn.document360.io/0108e24e-b3e8-446c-b670-66b1d2a9e861/Images/Documentation/image(587).png) In the right panel, add your **DocuWare URL** to the application ID URI and **Save.** ![](https://cdn.document360.io/0108e24e-b3e8-446c-b670-66b1d2a9e861/Images/Documentation/image(588).png) Next, add the **access_as_user** scope and fill the data in the right pane, for example: - **Scope name**: add “access_as_user”. - **Who can consent**: choose the option “Admins and users”. - **Admin consent display name**: fill with “Read-only access to user emails and profiles”. - **Admin consent description:** use the description “Allow DocuWare for Outlook to have read-only access to users’ emails and profiles”. - **User consent display name**: fill with “Read-only access to your emails and profile”. - **User consent description**: use the description “Allow DocuWare for Outlook to have read-only access to your emails and profiles”. - **State**: choose the option “Enabled”. ![](https://cdn.document360.io/0108e24e-b3e8-446c-b670-66b1d2a9e861/Images/Documentation/image(589).png) Click **Add a client application** and enter the following ID to pre-authorize all Microsoft Office application endpoints. ```plaintext ea5a67f6-b6f3-4338-b240-c655ddc3cc8e ``` This ID is valid for all Microsoft application endpoints. ![](https://cdn.document360.io/0108e24e-b3e8-446c-b670-66b1d2a9e861/Images/Documentation/image(591).png) ### 2. Authentication #### Redirecting Uris Switch to the **Authentication** tab and add the following redirect URIs to the OAuth application registration. ```plaintext https://YOUR_DOCUWARE_URL/DocuWare/Outlook-Frontend/        https://YOUR_DOCUWARE_URL/DocuWare/Outlook-Frontend/auth        https://YOUR_DOCUWARE_URL/DocuWare/Outlook-Frontend/login        https://YOUR_DOCUWARE_URL/DocuWare/Outlook-Frontend/adminConsentResult.html        brk-multihub://YOUR_DOCUWARE_URL ``` ![](https://cdn.document360.io/0108e24e-b3e8-446c-b670-66b1d2a9e861/Images/Documentation/image(592).png) > [!NOTE] > Note: entering a link without HTTPS > > Depending on the administrator’s Microsoft version and region, the Authentication tab in Azure might show a different view. In the new default view it's not possible to add the **brk-multihub://**. In this case, use the link **To switch to the old experience, please click here** to enter the **brk-multihub://** URL in the previous interface. #### Implicit grant and hybrid flows In the same page, switch to **Settings** section and make sure that **Access Tokens** and **ID Tokens** are activated. ![](https://cdn.document360.io/0108e24e-b3e8-446c-b670-66b1d2a9e861/Images/Documentation/image(609).png) ### 3. Creating a client secret For secure connection to your Office 365 account, DocuWare for Outlook requires a secret that will also be required in a later step. ![](https://cdn.document360.io/0108e24e-b3e8-446c-b670-66b1d2a9e861/Images/Documentation/image(594).png) ### 4. API Scopes #### 4.1 Configuring Microsoft APIs Switch to the **API** permissions tab to define the API permissions required by DocuWare for Outlook. Those are all to be added as **Microsoft Graph API permissions.** - email - offline_access - openid - profile - Contacts.Read - Contacts.Read.Shared - MailboxSettings.Read - MailboxSettings.ReadWrite - Mail.Read - Mail.ReadWrite - Mail.ReadWrite.Shared - User.Read ![](https://cdn.document360.io/0108e24e-b3e8-446c-b670-66b1d2a9e861/Images/Documentation/image(595).png) #### 4.2 APIs your organization uses Click again on **Add a permission**, switch to **APIs my organization uses,** type in the name of the OAuth app you are currently creating, for example “DocuWare for Outlook on-premises”. Then click on the entry in the result list. ![](https://cdn.document360.io/0108e24e-b3e8-446c-b670-66b1d2a9e861/Images/Documentation/image(596).png) Finally, check **access_as_user** and click on **Add permission**. ![](https://cdn.document360.io/0108e24e-b3e8-446c-b670-66b1d2a9e861/Images/Documentation/image(597).png) ### 5. Granting admin consent to the OAuth app Make sure to record the following values, generated in the beginning of the set up, when you created the OAuth app registration for the DocuWare on-premises system in Microsoft Entra. You will need them in the next steps: - Microsoft Tenant ID (tenantid) - Application Client ID (clientid) - Application Client Secret Completing this action finalizes the admin-consent process. After granting consent, you should see a confirmation screen like the one shown below. This step has to be made by the Microsoft Azure AD Global Admin. ![](https://cdn.document360.io/0108e24e-b3e8-446c-b670-66b1d2a9e861/Images/Documentation/image(598).png) ## On the DocuWare Server ### 1. Extending dwmachine.config Switch to the server where DocuWare is installed and open a PowerShell terminal with administrative rights on the folder where **DocuWare.Setup.Server.Cmd.exe** is located (i.e., C:\Program Files (x86)\DocuWare\Setup Components). Execute these commands to add required values to your server’s dwmachine.config file. ```plaintext ./DocuWare.Setup.Server.Cmd.exe configureMachine --key="D4O.TenantId" --value="theTenantGuid" ``` ```plaintext ./DocuWare.Setup.Server.Cmd.exe configureMachine --key="D4O.OfficeClientId" --value="theClientId" ``` ```plaintext ./DocuWare.Setup.Server.Cmd.exe configureMachine --key="D4O.OfficeClientSecret" --value="theClientSecret" --encrypted ``` ### 2. Enabling HTTPS for LocalWebServices and AuthorityAddress As Outlook requires having your application hosted via https, it's crucial to have the URL working & stated as **HTTPS**. ### 3. Creating Outlook Manifest.xml file You can create the Outlook **manifest.xml** file automatically or manually: #### **Generate the manifest file** Go to the Manifest Creation App website to generate the file without manually editing the XML: - Open the [DocuWare for Outlook - Manifest Creation](https://d4o-manifest.docuware.com/). - Enter your DocuWare organization URL and the DocuWare version you are using. - If the **Manifest ID** field is empty, click the refresh icon to generate a random ID. - Enter the **Client ID** you created in the [Microsoft Entra OAuth app registration](https://knowledgecenter.docuware.com/docs/install-docuware-for-outlook-on-premises#microsoft-entra-oauth-app-registration) step. - Click **Generate Manifest**. The XML file downloads automatically. Do not edit the Advanced Settings section; these fields are relevant only for specific test scenarios. ## Rollout of Add-In for Office 365 users Now that all requirements are set, the manifest file with your DocuWare system values can be used to be rolled out to Office 365 users. Just follow the [step-by-step description of the setup and roll-out process](https://knowledgecenter.docuware.com/docs/set-up-docuware-for-outlook). ## Supported versions: DocuWare on-premises 7.15 + 7.14 + 7.13 Access rights assigned to users that determine what actions they can perform within a system.