--- title: "Creating a single tenant app registration to use with PnP PowerShell to connect to SharePoint Online" canonical_url: "https://www.nutrient.io/guides/document-editor/troubleshooting/creating-pnp-powershell-app-registration/" md_url: "https://www.nutrient.io/guides/document-editor/troubleshooting/creating-pnp-powershell-app-registration.md" last_updated: "2026-05-23T00:08:18.035Z" description: "Solutions for common issues and errors in Nutrient Document Editor SDK with debugging tips and workarounds." --- The article provides detailed instructions on setting up a single-tenant app registration in Entra ID for use with PnP PowerShell to connect to SharePoint Online. This is necessary following recent changes (effective 9 September 2024) due to the deletion of the multi-tenant Entra ID application previously used by PnP PowerShell. Read the announcement [here](https://pnp.github.io/blog/post/changes-pnp-management-shell-registration/). It has always been a recommended practice to register your own Entra ID application to use with PnP PowerShell. This has now become [a mandatory step](https://github.com/pnp/powershell/issues/4250). Document Editor installers need to connect to your SharePoint Online environment, where you’ll be asked for a client ID, certificate path, certificate password, and tenant domain. If you’ve already created an app registration in your tenant, you can use its credentials. If not, read on to learn how you can create the app registration and obtain the required credentials. ## How to create the app registration 1. Start by registering a new single tenant app registration in Entra ID.![](/images/guides/document-editor/troubleshooting/creating-pnp-powershell-app-registration-1.png) 2. Create a self-signed certificate on your local machine using the PowerShell script found [here](https://learn.microsoft.com/en-us/sharepoint/dev/solution-guidance/security-apponly-azuread). Copy the script linked above, and paste it into a text editor — for example, Notepad. Save it as a `.ps1` file, e.g. `Create-SelfSignedCertificate.ps1`. Start Windows PowerShell as an administrator and navigate to the script location. Then, execute the following command: ```.\Create-SelfSignedCertificate.ps1 -CommonName "MyCompanyName" -StartDate 2024-09-19 -EndDate 2025-09-18 ``` You’ll be asked to give a password to encrypt your private key. Then, both the `.pfx` file and the `.cer` file will be generated and exported to the current folder. Don’t use special characters in the encryption password. Be sure to provide your company name or domain in `-CommonName`.![](/images/guides/document-editor/troubleshooting/creating-pnp-powershell-app-registration-2.png) For more information on creating self-signed certificates, see [this Microsoft article](https://learn.microsoft.com/en-us/sharepoint/dev/solution-guidance/security-apponly-azuread). 3. Associate the self-signed certificate (`.cer`) with the app registration created in the first step above. In Entra ID, go to **App registrations**. If you don’t see this in your **Owned applications**, go to **All applications**. Open the app registration you created and click **Add a certificate or secret**.![](/images/guides/document-editor/troubleshooting/creating-pnp-powershell-app-registration-3.png) Click **Certificates** > **Upload certificate**. Use the folder button to the right of the **Upload** field to bring up the **Open dialog** box, navigate to where your `.cer` file is located, and click **Open**.![](/images/guides/document-editor/troubleshooting/creating-pnp-powershell-app-registration-4.png) After selecting your certificate and entering a description (optional), click **Add**. 4. Add the permissions for the app. After adding the certificate, select **API permissions** from the left-hand menu to grant the required permissions for the app. Go to **Add a permission** > **Microsoft Graph** > **Application permissions**. Add the permissions for **Sites.FullControl.All** and **User.Read.All**. Then click to add or update permissions. Go to **Add a permission** > **SharePoint** > **Application permissions**. Add the permissions for **Sites.FullControl.All** and **User.Read.All**. Then click to add or update permissions.![](/images/guides/document-editor/troubleshooting/creating-pnp-powershell-app-registration-5.png) The status of all permissions will show a warning that it needs admin consent. Click **Grant admin consent** and the status should all show green checkmarks.![](/images/guides/document-editor/troubleshooting/creating-pnp-powershell-app-registration-6.png) 5. Run the installer to create or update the SPFx app in your tenant. The script requires the following parameters: - The client ID of the app registration created in the first step. - The full path to the `.pfx` self-signed certificate, e.g. `C:\folderName\certificateName.pfx`. - The password used to create the certificate. - Your tenant domain. To retrieve it, click the gear icon in `portal.azure.com` and check the **Domain** field.![](/images/guides/document-editor/troubleshooting/creating-pnp-powershell-app-registration-7.png) If you encounter any issues, [contact our customer support](https://support.nutrient.io/hc/en-us/requests/new). --- ## Related pages - [PDF viewer stuck on loading](/guides/document-editor/troubleshooting/pdf-viewer-stuck-on-loading.md) - [Resetting the SPO file handler cache](/guides/document-editor/troubleshooting/resetting-muhimbi-cache.md) - [Something went wrong, or resource object not found](/guides/document-editor/troubleshooting/something-went-wrong-or-resource-object-not-found.md) - [Uninstalling Nutrient Document Editor for SharePoint, Teams, and OneDrive](/guides/document-editor/troubleshooting/uninstalling-pdf-editor.md) - [Installing PDF Editor for SharePoint Online](/guides/document-editor/troubleshooting/installing-pdf-editor-for-sharepoint-online.md)