Let's get your portal live.
Deploy the Basewiser portal into your own Azure environment in a few minutes. Pick the way you'd rather run it — all three do exactly the same thing.
Open PowerShell 7
Launch pwsh — not "Windows PowerShell" 5.1, which the script will refuse. Check what you have:
$PSVersionTable.PSVersion
Don't have it? On Windows: winget install --id Microsoft.PowerShell. On macOS or Linux, follow Microsoft's install guide.
Run the setup command
iwr https://get.basewiser.com/setup.ps1 -OutFile setup.ps1; ./setup.ps1
Downloads the script and runs it in one go. It checks for the Azure CLI and the Az PowerShell modules, offers to install anything missing, and signs you in to Azure if you aren't already — all before it changes anything.
Answer a few prompts
Choose your subdomain, confirm your subscription, and pick your Azure region (defaults to norwayeast, or type any region you prefer).
You're live. Add your first customer
Your branded portal comes up at <subdomain>.basewiser.com — built from the subdomain you chose in step 3. Sign in and add your first customer tenant to get started.
Open Azure Cloud Shell
Go to shell.azure.com and sign in to your own Azure. Make sure you're in the tenant you want Basewiser to live in. First time? Choose PowerShell and No storage required.
Paste the setup command and press Enter
iwr https://get.basewiser.com/setup.ps1 -OutFile setup.ps1; ./setup.ps1
Downloads the script from this page, then runs it. It checks everything it needs before it changes anything.
Answer a few prompts
Choose your subdomain, confirm your subscription, and pick your Azure region (defaults to norwayeast, or type any region you prefer).
You're live. Add your first customer
Your branded portal comes up at <subdomain>.basewiser.com — built from the subdomain you chose in step 3. Sign in and add your first customer tenant to get started.
Download the package
Byte-for-byte the same script the command fetches — just delivered as something you can hand to whoever needs to sign off.
basewiser-setup.zip setup.ps1 · README.txtExtract it
On Windows, right-click the file and choose Extract All. Or from a terminal:
Expand-Archive basewiser-setup.zip -DestinationPath basewiser-setup
Read it before you run it
README.txt says in plain words what the script creates, and what it never sends. setup.ps1 is a single self-contained file with no hidden downloads — read it top to bottom. Nothing happens until you run it.
Open PowerShell 7 in that folder
Launch pwsh — not "Windows PowerShell" 5.1, which the script will refuse — and cd to where you extracted it.
Run it, then answer a few prompts
./setup.ps1
It checks for the Azure CLI and the Az PowerShell modules, offers to install anything missing, and signs you in to Azure if you aren't already. Then it asks for your subdomain, your subscription, and your Azure region (defaults to norwayeast).
You're live. Add your first customer
Your branded portal comes up at <subdomain>.basewiser.com — built from the subdomain you chose in step 5. Sign in and add your first customer tenant to get started.
- Asks you for a subdomain, your subscription, and your Azure region
- Deploys the portal into your own Azure subscription, in the tenant and region you choose
- Pulls the app images from the public GitHub Container Registry — no credentials needed
- Gates the portal behind your Entra ID sign-in, limited to a Basewiser Operators group
- Points
<subdomain>.basewiser.comat your new portal
It runs entirely under your Azure account. Your tenant and security data never leave your environment. Want to read the whole thing first? .
The script says exactly what to fix, and it's safe to re-run — it reuses anything it already created rather than duplicating it. Still stuck? Mail contact@basewiser.com and we'll get you live.
PowerShell says the script is blocked or won't run
Windows tags anything downloaded from the web, and a strict execution policy will stop it. Clear the tag on the file:
Unblock-File ./setup.ps1
If the policy is the problem, allow it for this window only — it reverts the moment you close the terminal:
Set-ExecutionPolicy -Scope Process RemoteSigned
I'm on Windows PowerShell 5.1
The script needs PowerShell 7 and stops with a message rather than failing halfway. On Windows: winget install --id Microsoft.PowerShell, then relaunch with pwsh. Azure Cloud Shell already runs 7 if you'd rather not install anything.
What permissions do I need on the subscription?
Contributor or Owner to create the resources, plus Owner or User Access Administrator to grant the portal's managed identity access to its own storage and Service Bus.
If those roles are governed by PIM, activate them before you start. The script verifies this up front, so a missing role surfaces in seconds rather than after it has provisioned half the stack.
How long does it take?
Five to ten minutes, most of it Azure provisioning while you wait.
Can I run it again?
Yes — it's safe to re-run. Anything it already created is reused rather than duplicated, so re-running after a failure picks up where it stopped instead of starting over.
I have several tenants or subscriptions
The script lists every subscription your account can see and asks which one to deploy into, then aligns the Azure CLI to match — so the deployment can't quietly land somewhere you didn't choose. Make sure you're signed in to the right tenant before you start; that's the one thing it can't switch for you.