This article lists common errors encountered when running the CreateAzureAdAppPermissionOnSites.ps1 script, which is used to grant administrator rights to the Jint Deployment application on your SharePoint app catalog, and explains how to resolve them.

📌 As a reminder, the context for using this script is described in the article Jint SharePoint – Prerequisites and Installation on Tenant.

In this article:

• Reminder: How to Run the Script
• Error: "The file is not digitally signed"

Reminder: How to Run the Script

Before running the script, make sure you have extracted it from the ZIP archive into a folder of your choice. A file that is not extracted (still inside the ZIP) can cause execution errors.

⚠️ The script must be run from Windows PowerShell (not from PowerShell 7, VS Code, or any other terminal). This is necessary for the Microsoft authentication window to display properly and allow you to sign in with your Entra ID administrator account.

The command to run should be in the following form:

.\CreateAzureAdAppPermissionOnSites.ps1 <App catalog site URL>

How to find the app catalog URL?
Go to the SharePoint Admin Center > More features > Apps > Open. The catalog URL will be in the format:
https://<your-tenant>.sharepoint.com/sites/appcatalog 

Error: "The file is not digitally signed"

When running the script, you might see the following message:

cannot be loaded. The file is not digitally signed. You cannot run this script on the current system.

This means that the PowerShell execution policy on your machine is blocking scripts that are not digitally signed. Several solutions are possible.

Option 1 — Unblock the File via PowerShell

This method targets only the downloaded script without changing your system's global settings.

1. Open PowerShell as an administrator
2. Run the following command, replacing the path with that of your script:

Unblock-File -Path "C:\path\to\CreateAzureAdAppPermissionOnSites.ps1"

3. Then run the script normally again.

Option 2 — Temporarily Change the Execution Policy

If the previous options don’t work, you can allow running local unsigned scripts for your current session only:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

Then run the script again. This change applies only to your user account and does not modify global system settings.

Option 3 — One-Time Execution Without Changing Policy

For a single execution without any configuration changes:

powershell.exe -ExecutionPolicy Bypass -File "C:\path\to\CreateAzureAdAppPermissionOnSites.ps1" <App catalog URL>

⚠️ These operations require an account with local administrator rights on the machine. If you do not have these rights, please contact your IT team.