--- title: "DLP Tags Entra ID App Registration" slug: "dlp-tags-entra-id-app-registration" tags: ["DLP Tags", "Entra Identity", "Azure Integration"] updated: 2026-10-21T17:10:11Z published: 2026-10-21T17:10:11Z canonical: "docs.eshare.com/dlp-tags-entra-id-app-registration" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.eshare.com/llms.txt > Use this file to discover all available pages before exploring further. # DLP Tags Entra ID App Registration This document describes the steps to create a custom eSHARE DLP Tags application in the Microsoft Entra (Azure AD) portal. The following steps will be reviewed: - [Register the Application](/collaborate/docs/dlp-tags-entra-id-app-registration#application-registration) - [Modify the Application Manifest - Commercial Cloud](/collaborate/docs/dlp-tags-entra-id-app-registration#modify-application-manifest-commercial-cloud) - [Modify the Application Manifest - Government Cloud](/collaborate/docs/dlp-tags-entra-id-app-registration#modify-application-manifest-government-cloud) - [Grant Admin Consent for API Permissions](/collaborate/docs/dlp-tags-entra-id-app-registration#review-api-permissions-and-complete-consent) - [Assign the Security Reader Role](/collaborate/docs/dlp-tags-entra-id-app-registration#provide-security-reader-role-access) - [Upload the Application Certificate or Client Secret](/collaborate/docs/dlp-tags-entra-id-app-registration#upload-application-certificate-or-client-secret) - [Collect the Values Required for the eSHARE DLP Tags Service](/collaborate/docs/dlp-tags-entra-id-app-registration#collect-items-required-for-eshare-dlp-tags-service) > **PREREQUISITES:** > > The person performing these steps must have an administrator role assignment of **Application Administrator**, **Cloud Application Administrator**, or **Global Administrator** in the destination M365 tenant. > [!WARNING] > Note: Reuse your existing eSHARE Collaborate app registration, or create a new one? > > If your organization already has an **eSHARE Collaborate** App Registration in Microsoft Entra (created during initial eSHARE onboarding), you can reuse that same application for the DLP Tags integration instead of creating a new, separate one. Add the same API permissions and role assignment described in [Modify the Application Manifest - Commercial Cloud](/collaborate/docs/dlp-tags-entra-id-app-registration#modify-application-manifest-commercial-cloud) (or the [Government Cloud](/collaborate/docs/dlp-tags-entra-id-app-registration#modify-application-manifest-government-cloud) equivalent) to that existing app registration, then skip ahead to [Assign the Security Reader Role](/collaborate/docs/dlp-tags-entra-id-app-registration#provide-security-reader-role-access). > > If you would rather create a separate, dedicated application for DLP Tags, start from [Register the Application](/collaborate/docs/dlp-tags-entra-id-app-registration#application-registration) below. ### **Register the Application** 1. Sign in to the Microsoft Entra admin center ([https://entra.microsoft.com](https://entra.microsoft.com/) or [https://entra.microsoft.us](https://entra.microsoft.us)) and navigate to '**Applications**' > '**App Registrations**'. 2. On the '**App Registrations**' page, click the '**+ New registration**' button in the top menu bar. 3. Enter a recognizable, unique name for the custom eSHARE DLP Tags app and select the '**Register**' button at the bottom of the page. In a few moments, a shell application is created and ready for further configuration. ### **Modify the Application Manifest - Commercial Cloud** 1. On the newly registered application page, navigate to the '**Manage**' > '**Manifest**' tab. 2. In the application's manifest, look for '**requiredResourceAccess**'. ![](https://cdn.us.document360.io/c516537f-0d2f-4bf8-930d-3385ca9a11d7/Images/Documentation/CleanShot 2025-11-16 at 11.20.54@2x.png?sv=2026-02-06&spr=https&st=2026-11-18T20%3A23%3A02Z&se=2026-11-18T21%3A23%3A02Z&sr=b&sp=r&sig=z42%2BYb%2F9p%2BCZA40x9bwEOuTolxeQpMVemHMpqMbYGIM%3D) 1. Replace the above string (including the comma at the end) from line 53 to 63 with the text below. ```json "requiredResourceAccess": [ { "resourceAppId": "00000003-0000-0000-c000-000000000000", "resourceAccess": [ { "id": "e1fe6dd8-ba31-4d61-89e7-88639da4683d", "type": "Scope" } ] }, { "resourceAppId": "00000002-0000-0ff1-ce00-000000000000", "resourceAccess": [ { "id": "dc50a0fb-09a3-484d-be87-e023b12c6440", "type": "Role" } ] }, { "resourceAppId": "c5393580-f805-4401-95e8-94b7a6ef2fc2", "resourceAccess": [ { "id": "594c1fb6-4f81-4475-ae41-0c394909246c", "type": "Role" }, { "id": "4807a72c-ad38-4250-94c9-4eabfe26cd55", "type": "Role" } ] } ], ``` 1. Click the '**Save**' button in the top menu bar. ### **Modify the Application Manifest - Government Cloud** 1. On the newly registered application page, navigate to the '**Manage**' > '**Manifest**' tab. 2. In the application's manifest, look for '**requiredResourceAccess**'. ![](https://cdn.us.document360.io/c516537f-0d2f-4bf8-930d-3385ca9a11d7/Images/Documentation/CleanShot 2025-11-16 at 11.34.08@2x.png?sv=2026-02-06&spr=https&st=2026-11-18T20%3A23%3A02Z&se=2026-11-18T21%3A23%3A02Z&sr=b&sp=r&sig=o4XBFVWex7bynvelrjcMol1JviI866Bfa92sn5FJZOY%3D) 1. Replace the above string (including the comma at the end) from line 42 to 52 with the text below. ```json "requiredResourceAccess": [ { "resourceAppId": "00000003-0000-0000-c000-000000000000", "resourceAccess": [ { "id": "e1fe6dd8-ba31-4d61-89e7-88639da4683d", "type": "Scope" } ] }, { "resourceAppId": "00000002-0000-0ff1-ce00-000000000000", "resourceAccess": [ { "id": "dc50a0fb-09a3-484d-be87-e023b12c6440", "type": "Role" } ] }, { "resourceAppId": "c5393580-f805-4401-95e8-94b7a6ef2fc2", "resourceAccess": [ { "id": "594c1fb6-4f81-4475-ae41-0c394909246c", "type": "Role" }, { "id": "4807a72c-ad38-4250-94c9-4eabfe26cd55", "type": "Role" } ] } ], ``` 1. Click the '**Save**' button in the top menu bar. ### **Grant Admin Consent for API Permissions** > **REQUIREMENT:** > > Granting admin consent for permissions within an app registration must be performed by a **Global Administrator** in the destination M365 tenant. > [!WARNING] > Important: > > Please consult your eSHARE Customer Success Manager before removing any API permissions. 1. For the saved application, navigate to the '**Manage**' > '**API permissions**' tab. 2. Select '**Grant admin consent for **' at the top of the API permissions table. 3. Confirm when prompted. ![](https://cdn.us.document360.io/c516537f-0d2f-4bf8-930d-3385ca9a11d7/Images/Documentation/image-1788537759764.png?sv=2026-02-06&spr=https&st=2026-11-18T20%3A23%3A02Z&se=2026-11-18T21%3A23%3A02Z&sr=b&sp=r&sig=e7WGJhTolcMYGOKu3%2B385cNxQoAUolwee93o1bueO%2BM%3D) ### **Assign the Security Reader Role** In addition to the required API permissions, the Entra ID application must be assigned the '**Security Reader**' privileged role. 1. Navigate to '**Entra ID**' > '**Roles & Admins**'. 2. Assign the Security Reader role, and give the DLP Tags application a permanent role assignment. ![](https://cdn.us.document360.io/c516537f-0d2f-4bf8-930d-3385ca9a11d7/Images/Documentation/CleanShot 2025-12-06 at 11.27.49@2x.png?sv=2026-02-06&spr=https&st=2026-11-18T20%3A23%3A02Z&se=2026-11-18T21%3A23%3A02Z&sr=b&sp=r&sig=Y7%2FUhSHy4sbekAuiaQ7P18onIjJRXHjL2ZYyapXoaNo%3D) ### **Upload the Application Certificate or Client Secret** Obtain a credential using one of the following options: - **Option 1**: Purchase a certificate from a well-known certificate authority and extract the private and public portions of the certificate. Upload the public portion in the Azure portal for the application and upload the private key in your eSHARE Admin Console (or provide the private key to your eSHARE admin). - **Option 2**: Create a self-signed certificate by following the instructions available at [https://learn.microsoft.com/en-us/azure/active-directory/develop/howto-create-self-signed-certificate](https://learn.microsoft.com/en-us/azure/active-directory/develop/howto-create-self-signed-certificate). - **Option 3**: Generate a Client Secret. A short summary of the instructions for options 1 and 2 is below. ```powershell # Create a self-signed certificate in PowerShell $mycert = "eShareApp" $mycert = New-SelfSignedCertificate -DnsName "eShareApp" -Subject "CN=eShareApp" -CertStoreLocation "Cert:\CurrentUser\My" -NotAfter (Get-Date).AddYears(50) -KeyExportPolicy Exportable -KeySpec Signature -KeyLength 2048 -KeyAlgorithm RSA -HashAlgorithm SHA256 ``` ```powershell # Extract .key file using OpenSSL openssl pkcs12 -in eShareApp.pfx -nocerts -nodes -out eShareApp.key ``` ```powershell # Extract crt from pfx using OpenSSL openssl pkcs12 -in eShareApp.pfx -clcerts -nokeys -out eShareApp.crt ``` ```powershell # Export certificate to .pfx file $mycert | Export-PfxCertificate -FilePath eShareApp.pfx -Password $(ConvertTo-SecureString -String "myp@55W0rd" -AsPlainText -Force) ``` 1. When the appropriate certificate portions are available, navigate to '**Manage**' > '**Certificates & secrets**'. 2. On the '**Certificates**' tab, click the '**Upload certificate**' button. 3. Upload the CRT file from the steps above and click '**Add**' at the bottom of the open pane. ### **Collect the Values Required for the eSHARE DLP Tags Service** Collect and save the following values: - **M365 Tenant ID**: Navigate to the '**Identity**' > '**Overview**' tab of the Entra admin center, copy the '**Tenant ID**' and save it. - **Application ID**: Navigate to the '**Overview**' tab of the application, copy the '**Application (client) ID**' and save it. - **Certificate Thumbprint**: For the certificate used during the application registration process, copy the certificate thumbprint and save it. - **Private Key**: The private key (.key file from the steps above) for the certificate uploaded in the Entra portal for the application registration. - **Client Secret**: Only if the organization has opted for this method instead of a certificate; not required if a certificate is in use. ## Related - [Create eShare Entra ID App Registration](/create-eshare-entra-id-app-registration.md)