Skip to content

First setup and sign-in

The first administrator

A new instance has no account. The sign-in page shows First-run setup and asks for the Setup code. The backend writes this code to its log at every start (docker logs <backend container>), or it is the value of SETUP_CODE in the environment. With the code you have two ways:

  • Sign in with Microsoft (recommended): you become the first administrator, and from then on only people of your Microsoft organisation can sign in. A Microsoft work account is needed; personal accounts are refused.
  • or create a local administrator: email and password (at least 12 characters).

Afterwards the setup is closed; a second attempt shows "The setup is already completed".

Setup wizard

Right after the first sign-in, Atrium opens the Setup wizard for administrators. It walks through the steps below; each step shows the same block as in the settings, so nothing is set up twice. Optional steps have Skip. Later closes the wizard, and it opens again at the step where you stopped. You can go through it again at any time with Setup wizard at the top of Settings.

Step What you do
Tenant Add the tenant whose virtual desktops Atrium looks after and connect it (see Tenants and connection). Continue works once a tenant exists.
Roles from Entra ID (optional) Add your Microsoft tenant so that the Entra app roles of your team count (see Accounts and roles).
License (optional) Enter the license key from Scalio Compass. Without a key Atrium runs as Community edition (see License).

An instance that was already in use before this version counts as set up: the wizard does not open by itself there.

Sign-in with a password

Accounts and roles → Sign-in (administrators) decides who may sign in with a password:

Setting Effect
Allowed Password and passkeys work for every local account.
Only emergency administrator Everybody signs in with Microsoft, except administrators marked as Emergency administrator.
Off (Microsoft only) Passwords and passkeys no longer work.

The two stricter values can be chosen only once at least one emergency administrator exists.

Mark at least one administrator with a password as Emergency administrator: that account is the way in when Microsoft cannot be reached.

Locked out?

If sign-in with a password is off and Microsoft is unreachable, set FORCE_LOCAL_LOGIN=true in the environment of the backend and restart it. Passwords then work for everybody, and Atrium shows a warning until you remove the setting again.

E-mail sending

Use the default (recommended): You set up sending once for all Scalio apps: for SaaS in Scalio Compass under Microsoft tenants → E-mail sending for all apps, for self-hosted in the installation's mail.env file. With this choice the app takes over that default; the page shows where it comes from and which sender is used. New installations start with this choice; without a default the app sends nothing. If Scalio has switched on «Through Scalio» for your organization and you have not set a default of your own, the app sends through Scalio (sender noreply@scaliocloud.com, «Your name über Scalio»). If you pick a way of your own below, it applies to this app only, for example for a different sender mailbox.

Settings → Notifications → E-mail sending (administrators): choose SMTP server (server, port, encryption, user name, password) or Microsoft 365 (tenant ID, client ID, client secret, sending mailbox), plus sender address and name, and check it with Send test mail. Password and client secret are stored encrypted and never shown again. Last mails shows what was sent; Atrium retries a failed mail up to five times.

Microsoft 365 through the tenant connection sends with the connection of a connected tenant, with no second app registration and no secret: choose the Tenant that sends and the Sending mailbox (for example a shared mailbox it@…) and save. Then give the send right under Send right in Exchange Online with Show script (Set send right stays greyed out because the connection only reads): run the script once as an Exchange administrator in Azure Cloud Shell or in PowerShell 7 on your computer; it installs missing modules itself and stops if there is no connection to Exchange Online. With RBAC for Applications it lets the app send only as this mailbox; no Mail.Send permission in Entra ID is needed. Exchange applies the right within up to two hours, then the test mail works. Run the script again after changing the mailbox. For Microsoft 365 with an own app registration the page shows the same script.

Second factor

Every person with a password can add an authenticator app, backup codes and passkeys under Profile → Security (see Signing in). Sign-in with Microsoft uses the second factor of your Microsoft organisation.