First-Time Setup Guide
You are helping a non-technical user get the Power Automate plugin working for the first time. Be friendly, use plain language, and never assume they know terminal commands. Walk them through each step one at a time.
Step 1: Check Node.js
Run silently:
node --version 2>&1
- If it works (prints something like
v18.x.x or higher): Tell them "Node.js is installed" and move on.
- If it fails or version is below 18: Tell them they need Node.js 18 or newer. Ask what operating system they're on, then give them the simplest install instructions:
- Windows: "Go to https://nodejs.org, download the LTS version, and run the installer. Click Next through everything."
- Mac: "Open Terminal and run:
brew install node" (or direct them to nodejs.org)
- After they've installed it, re-check with
node --version.
Step 2: Check Azure CLI
Run silently:
az --version 2>&1
- If it works: Tell them "Azure CLI is installed" and move on.
- If it fails: Tell them they need the Azure CLI. Ask their OS:
- Windows: "Open PowerShell as administrator and run:
winget install Microsoft.AzureCLI" or direct them to https://aka.ms/installazurecliwindows
- Mac: "
brew install azure-cli"
- After install, re-check with
az --version.
Step 3: Azure Login
Check if they're already logged in:
az account show --output json 2>&1
- If it works (shows account info): Tell them who they're logged in as (show the
user.name field) and ask if that's the right account.
- If it fails: Tell them "Let's sign you into Azure." Then run:
az login
This will open their browser. Tell them: "A browser window should open. Sign in with your work account — the one you use for Power Automate."
After login completes, confirm it worked by running az account show again.
Verify token access — this catches permission issues early.
First find out which Azure cloud they're on, because the Power Automate
resource URL differs per cloud and the commercial one cannot be assumed
(GCC High / DoD tenants will fail against it):
az cloud show --query name -o tsv
az cloud show |
Power Automate resource |
AzureCloud (commercial) |
https://service.flow.microsoft.com |
AzureCloud + GCC tenant |
https://gov.service.flow.microsoft.us |
AzureUSGovernment (GCC High) |
https://high.service.flow.microsoft.us |
AzureUSGovernment (DoD) |
Operator-verified PA_FLOW_RESOURCE value required; no built-in audience |
az cloud show cannot distinguish commercial from GCC, or GCC High from DoD —
for those, set PA_CLOUD=gcc / PA_CLOUD=dod explicitly.
DoD endpoint hosts use appsplatform.us, but that does not establish the token
audience (App ID URI). With PA_CLOUD=dod, FlowAgent requires an explicit,
operator-verified PA_FLOW_RESOURCE and fails configuration otherwise. Do not
copy a guessed audience from a hostname; obtain the correct value for the tenant.
Then request a token for the matching resource, e.g. for commercial:
az account get-access-token --resource https://service.flow.microsoft.com --output json 2>&1
FlowAgent itself auto-detects the cloud the same way; you can override the
detection with PA_CLOUD=commercial|gcc|gcchigh|dod.
- If it works: Move on.
- If it fails with "AADSTS65002" (common in GCC High): the Azure CLI app isn't
preauthorized for the Power Automate resource in that cloud. This is not a license
problem. Register a public-client app with delegated Power Automate (Flow service)
permissions and set
PA_CLIENT_ID=<app-id>; flow commands then use that app.
- If it fails with any other "AADSTS": The user's account may not have Power Automate access. Tell them: "Your Azure account doesn't seem to have access to Power Automate. Check with your IT admin that you have a Power Automate license."
- If it fails with other errors: Show the error and suggest they contact IT support.
- If they're on a sovereign cloud and connection-management commands fail: keep
the original error and inspect its code.
AADSTS650057 can indicate an invalid
resource or missing app authorization; AADSTS65001 can require admin consent.
An app-not-found or consent failure may require an appropriately authorized
public-client registration and PA_CLIENT_ID=<app-id>. Network, tenant-selection
and expired-session errors need different remediation. Do not infer missing
preauthorization from the cloud name or classify every other code as unrelated.
Signing in to a specific account
Connection management authenticates separately from az — it uses its own MSAL
session with its own on-disk token cache, so az login / az account set do
not switch the account it uses.
Three tools cover this:
| Tool |
Use it to |
list_accounts |
See the cached-account inventory, effectiveConnectivityIdentity, and nextSignIn settings. Inactive tenant caches do not count as identity mismatches. Acquires no token. |
switch_account |
Save a preferred username, or omit it to clear the preference. Check preferencePersisted and nextSignIn: environment overrides still apply. |
whoami / doctor |
Compare the effective Connectivity username and tenant with Azure CLI, including different users in the same tenant. |
When a connection tool fails with ServiceToServiceEnvironmentNotFound,
check identity before assuming the environment is missing. list_accounts
distinguishes the effective account from historical cached accounts. A different
username or tenant on the effective account indicates a mismatch; an unused
tenant's cache alone does not. switch_account clears the cached sign-in and
records the preferred username for reauthentication. It does not prove that
the subsequent sign-in succeeded or that environment permissions are correct.
switch_account does not change the Azure CLI identity. az is yours to set;
where the two disagree, the tool says so rather than silently re-pointing one.
reconnect keeps a recorded preference — it drops credentials, and the
preference is a stated intent rather than a credential.
It waits for pending token acquisition and cache cleanup, then clears in-memory
tokens for all Azure CLI resources as well as Connectivity. A cleanup failure
is an error, not a completed switch: fix the cache access problem and retry.
Do not continue under the assumption that credentials changed when reset failed.
On interactive sign-in FlowAgent forces the account picker by default, so the
browser's currently-signed-in account is never used silently. Two overrides:
| Variable |
Effect |
PA_LOGIN_HINT=<upn> |
Pre-select that account. Suppresses the picker, since the account is already targeted. |
PA_NO_ACCOUNT_PICKER=1 |
Restore plain browser SSO. For single-account users who don't want the extra click. |
Precedence, most specific first: PA_LOGIN_HINT, then a switch_account
preference, then PA_NO_ACCOUNT_PICKER, then the picker.
For example, switch_account with username B still targets A if
PA_LOGIN_HINT=A is set. Omitting the username clears only the stored preference;
it does not override PA_LOGIN_HINT or PA_NO_ACCOUNT_PICKER. The response
reports the effective settings instead of promising a picker in those cases.
Step 4: Check the FlowAgent tools are wired
The plugin talks to Power Automate through the FlowAgent MCP server, which is
registered as flowagent in the plugin's .mcp.json and started automatically.
.mcp.json loads the bundled server/mcp.mjs through a small Node bootstrap
that resolves the plugin's installation directory (PLUGIN_ROOT, else
CLAUDE_PLUGIN_ROOT, else the current directory) and prints an actionable error
if the bundle can't be found.
If flowagent-* / mcp__flowagent__* tools appear in your tool list: tell
them "The Power Automate tools are connected" and move on.
If they're missing: the MCP server isn't registered. Fix it automatically:
Locate the installed plugin's MCP bundle. This only matches a bundle
inside a power-automate plugin directory, so it can't pick up another
plugin's MCP server:
node -e "const fs=require('fs'),p=require('path'),d=p.join(process.env.HOME||process.env.USERPROFILE,'.copilot','installed-plugins');const find=(dir)=>{let out=[];for(const e of fs.readdirSync(dir,{withFileTypes:true})){const f=p.join(dir,e.name);if(e.isDirectory()){try{out=out.concat(find(f))}catch{}}else if(e.name==='mcp.mjs'&&p.basename(p.dirname(dir))==='power-automate'){out.push(dir)}}return out};try{const hits=find(d);if(hits.length===1)console.log(JSON.stringify({found:true,serverDir:hits[0],mcpMjs:p.join(hits[0],'mcp.mjs')}));else if(hits.length>1)console.log(JSON.stringify({found:false,reason:'multiple power-automate bundles',candidates:hits}));else console.log(JSON.stringify({found:false}))}catch(e){console.log(JSON.stringify({found:false,error:e.message}))}"
If it reports multiple power-automate bundles, show the candidates and ask
the user which one to register rather than guessing.
If exactly one was found, read ~/.copilot/mcp-config.json, add the
flowagent MCP entry, and write it back:
node -e "const fs=require('fs'),p=require('path');const home=process.env.HOME||process.env.USERPROFILE;const cfgPath=p.join(home,'.copilot','mcp-config.json');let cfg;try{cfg=JSON.parse(fs.readFileSync(cfgPath,'utf8'))}catch{cfg={mcpServers:{}}};if(!cfg.mcpServers)cfg.mcpServers={};if(cfg.mcpServers.flowagent){console.log('already registered');process.exit(0)}const d=p.join(home,'.copilot','installed-plugins');const find=(dir)=>{let out=[];for(const e of fs.readdirSync(dir,{withFileTypes:true})){const f=p.join(dir,e.name);if(e.isDirectory()){try{out=out.concat(find(f))}catch{}}else if(e.name==='mcp.mjs'&&p.basename(p.dirname(dir))==='power-automate'){out.push(dir)}}return out};const hits=find(d);if(hits.length!==1){console.log(hits.length?'ambiguous: '+JSON.stringify(hits):'mcp.mjs not found');process.exit(1)}const mcpPath=p.join(hits[0],'mcp.mjs');cfg.mcpServers.flowagent={command:'node',args:[mcpPath]};fs.writeFileSync(cfgPath,JSON.stringify(cfg,null,2)+'\n');console.log('registered flowagent MCP at '+mcpPath)"
Tell the user to restart the agent (Copilot CLI: /restart, Claude Code:
restart the process). After restart, flowagent-* tools should appear.
If not found (plugin not installed at all): tell them to install the
plugin first:
/plugin marketplace add microsoft/power-platform-skills
Then select power-automate and run /setup again.
Step 5: Smoke Test
Verify everything works end-to-end by listing the user's environments:
Preferred: call the list_environments tool.
If MCP tools aren't available: run node <path-to-plugin>/server/mcp.mjs
to confirm the bundled MCP server starts cleanly, then fix the plugin install
or .mcp.json wiring before retrying.
If it returns environments: Success! Tell them:
- "Everything is working! Here are your Power Automate environments:"
- Show the environments in a simple table (name, location).
- If there are multiple, ask which one they mainly use and suggest setting it
as the default (the
set_current_env tool, or ask "set my default
environment to ").
- Tell them about the available skills:
/browse-flows — Browse your flows
/create-flow — Create a new flow
/debug-flow — Fix a broken flow
If it fails: Check the error. Common issues:
- Auth error → go back to Step 3
- Tools not found → go back to Step 4
- Network error → ask if they're behind a corporate proxy/VPN
Tone Guidelines
- Use "we" language: "Let's check if Node.js is installed"
- Celebrate small wins: "Great, Node.js is ready!"
- Don't dump all steps at once — do one at a time and confirm before moving on
- If something fails, don't panic — explain what went wrong in plain English and what to do
- Never show raw JSON errors to the user without explaining what they mean
1---2name: setup3description: Set up Power Automate CLI prerequisites. Use when the user is new, something isn't working, or they need help getting started.4user-invocable: true5allowed-tools: Bash, Read, Write, Glob, Grep, AskUserQuestion, mcp__flowagent__list_environments, mcp__flowagent__set_current_env, mcp__flowagent__get_current_env, mcp__flowagent__resolve_environment, mcp__flowagent__list_flows, mcp__flowagent__get_flow, mcp__flowagent__create_flow, mcp__flowagent__update_flow, mcp__flowagent__edit_flow, mcp__flowagent__copy_flow, mcp__flowagent__publish_flow, mcp__flowagent__disable_flow, mcp__flowagent__delete_flow, mcp__flowagent__run_flow, mcp__flowagent__get_run_history, mcp__flowagent__get_run_details, mcp__flowagent__get_run_actions, mcp__flowagent__get_run_action_repetitions, mcp__flowagent__cancel_run, mcp__flowagent__cancel_all_runs, mcp__flowagent__resubmit_run, mcp__flowagent__diagnose_run, mcp__flowagent__list_connections, mcp__flowagent__list_connectors, mcp__flowagent__get_connector, mcp__flowagent__search_operations, mcp__flowagent__get_operation_details, mcp__flowagent__pick_or_create_connection, mcp__flowagent__resolve_refs, mcp__flowagent__resolve_params, mcp__flowagent__scaffold_flow, mcp__flowagent__list_templates, mcp__flowagent__validate_flow, mcp__flowagent__preflight_flow, mcp__flowagent__smoke_test, mcp__flowagent__get_expression_help, mcp__flowagent__list_desktop_flows, mcp__flowagent__list_machine_groups, mcp__flowagent__run_desktop_flow, mcp__flowagent__get_flow_context, mcp__flowagent__set_current_flow, mcp__flowagent__clear_current_flow, mcp__flowagent__invoke_operation, mcp__flowagent__get_past_trigger_inputs, mcp__flowagent__test_connection, mcp__flowagent__fix_connection, mcp__flowagent__delete_connection, mcp__flowagent__preview_update, mcp__flowagent__get_backup, mcp__flowagent__list_backups, mcp__flowagent__restore_backup, mcp__flowagent__list_trigger_emulators, mcp__flowagent__whoami, mcp__flowagent__doctor, mcp__flowagent__reconnect, mcp__flowagent__list_accounts, mcp__flowagent__switch_account6model: opus7metadata:8 source: https://skillmd.com/skills/microsoft/setup9---1011# First-Time Setup Guide1213You are helping a non-technical user get the Power Automate plugin working for the first time. Be friendly, use plain language, and never assume they know terminal commands. Walk them through each step one at a time.1415## Step 1: Check Node.js1617Run silently:18```bash19node --version 2>&120```2122- **If it works** (prints something like `v18.x.x` or higher): Tell them "Node.js is installed" and move on.23- **If it fails or version is below 18**: Tell them they need Node.js 18 or newer. Ask what operating system they're on, then give them the simplest install instructions:24 - **Windows**: "Go to https://nodejs.org, download the LTS version, and run the installer. Click Next through everything."25 - **Mac**: "Open Terminal and run: `brew install node`" (or direct them to nodejs.org)26 - After they've installed it, re-check with `node --version`.2728## Step 2: Check Azure CLI2930Run silently:31```bash32az --version 2>&133```3435- **If it works**: Tell them "Azure CLI is installed" and move on.36- **If it fails**: Tell them they need the Azure CLI. Ask their OS:37 - **Windows**: "Open PowerShell as administrator and run: `winget install Microsoft.AzureCLI`" or direct them to https://aka.ms/installazurecliwindows38 - **Mac**: "`brew install azure-cli`"39 - After install, re-check with `az --version`.4041## Step 3: Azure Login4243Check if they're already logged in:44```bash45az account show --output json 2>&146```4748- **If it works** (shows account info): Tell them who they're logged in as (show the `user.name` field) and ask if that's the right account.49- **If it fails**: Tell them "Let's sign you into Azure." Then run:50 ```bash51 az login52 ```53 This will open their browser. Tell them: "A browser window should open. Sign in with your work account — the one you use for Power Automate."54 After login completes, confirm it worked by running `az account show` again.5556**Verify token access** — this catches permission issues early.5758First find out which Azure cloud they're on, because the Power Automate59resource URL differs per cloud and the commercial one cannot be assumed60(GCC High / DoD tenants will fail against it):61```bash62az cloud show --query name -o tsv63```6465| `az cloud show` | Power Automate resource |66|---|---|67| `AzureCloud` (commercial) | `https://service.flow.microsoft.com` |68| `AzureCloud` + GCC tenant | `https://gov.service.flow.microsoft.us` |69| `AzureUSGovernment` (GCC High) | `https://high.service.flow.microsoft.us` |70| `AzureUSGovernment` (DoD) | Operator-verified `PA_FLOW_RESOURCE` value required; no built-in audience |7172`az cloud show` cannot distinguish commercial from GCC, or GCC High from DoD —73for those, set `PA_CLOUD=gcc` / `PA_CLOUD=dod` explicitly.7475DoD endpoint hosts use `appsplatform.us`, but that does not establish the token76audience (App ID URI). With `PA_CLOUD=dod`, FlowAgent requires an explicit,77operator-verified `PA_FLOW_RESOURCE` and fails configuration otherwise. Do not78copy a guessed audience from a hostname; obtain the correct value for the tenant.7980Then request a token for the matching resource, e.g. for commercial:81```bash82az account get-access-token --resource https://service.flow.microsoft.com --output json 2>&183```84FlowAgent itself auto-detects the cloud the same way; you can override the85detection with `PA_CLOUD=commercial|gcc|gcchigh|dod`.86- **If it works**: Move on.87- **If it fails with "AADSTS65002"** (common in GCC High): the Azure CLI app isn't88 preauthorized for the Power Automate resource in that cloud. This is not a license89 problem. Register a public-client app with delegated Power Automate (Flow service)90 permissions and set `PA_CLIENT_ID=<app-id>`; flow commands then use that app.91- **If it fails with any other "AADSTS"**: The user's account may not have Power Automate access. Tell them: "Your Azure account doesn't seem to have access to Power Automate. Check with your IT admin that you have a Power Automate license."92- **If it fails with other errors**: Show the error and suggest they contact IT support.93- **If they're on a sovereign cloud and connection-management commands fail**: keep94 the original error and inspect its code. `AADSTS650057` can indicate an invalid95 resource or missing app authorization; `AADSTS65001` can require admin consent.96 An app-not-found or consent failure may require an appropriately authorized97 public-client registration and `PA_CLIENT_ID=<app-id>`. Network, tenant-selection98 and expired-session errors need different remediation. Do not infer missing99 preauthorization from the cloud name or classify every other code as unrelated.100101## Signing in to a specific account102103Connection management authenticates separately from `az` — it uses its own MSAL104session with its own on-disk token cache, so `az login` / `az account set` do105**not** switch the account it uses.106107Three tools cover this:108109| Tool | Use it to |110|---|---|111| `list_accounts` | See the cached-account inventory, `effectiveConnectivityIdentity`, and `nextSignIn` settings. Inactive tenant caches do not count as identity mismatches. Acquires no token. |112| `switch_account` | Save a preferred `username`, or omit it to clear the preference. Check `preferencePersisted` and `nextSignIn`: environment overrides still apply. |113| `whoami` / `doctor` | Compare the effective Connectivity username and tenant with Azure CLI, including different users in the same tenant. |114115**When a connection tool fails with `ServiceToServiceEnvironmentNotFound`**,116check identity before assuming the environment is missing. `list_accounts`117distinguishes the effective account from historical cached accounts. A different118username or tenant on the effective account indicates a mismatch; an unused119tenant's cache alone does not. `switch_account` clears the cached sign-in and120records the preferred username for reauthentication. It does not prove that121the subsequent sign-in succeeded or that environment permissions are correct.122123`switch_account` does not change the Azure CLI identity. `az` is yours to set;124where the two disagree, the tool says so rather than silently re-pointing one.125`reconnect` keeps a recorded preference — it drops credentials, and the126preference is a stated intent rather than a credential.127It waits for pending token acquisition and cache cleanup, then clears in-memory128tokens for all Azure CLI resources as well as Connectivity. A cleanup failure129is an error, not a completed switch: fix the cache access problem and retry.130Do not continue under the assumption that credentials changed when reset failed.131132On interactive sign-in FlowAgent forces the account picker by default, so the133browser's currently-signed-in account is never used silently. Two overrides:134135| Variable | Effect |136|---|---|137| `PA_LOGIN_HINT=<upn>` | Pre-select that account. Suppresses the picker, since the account is already targeted. |138| `PA_NO_ACCOUNT_PICKER=1` | Restore plain browser SSO. For single-account users who don't want the extra click. |139140Precedence, most specific first: `PA_LOGIN_HINT`, then a `switch_account`141preference, then `PA_NO_ACCOUNT_PICKER`, then the picker.142For example, `switch_account` with username B still targets A if143`PA_LOGIN_HINT=A` is set. Omitting the username clears only the stored preference;144it does not override `PA_LOGIN_HINT` or `PA_NO_ACCOUNT_PICKER`. The response145reports the effective settings instead of promising a picker in those cases.146147## Step 4: Check the FlowAgent tools are wired148149The plugin talks to Power Automate through the **FlowAgent MCP server**, which is150registered as `flowagent` in the plugin's `.mcp.json` and started automatically.151`.mcp.json` loads the bundled `server/mcp.mjs` through a small Node bootstrap152that resolves the plugin's installation directory (`PLUGIN_ROOT`, else153`CLAUDE_PLUGIN_ROOT`, else the current directory) and prints an actionable error154if the bundle can't be found.155156- **If `flowagent-*` / `mcp__flowagent__*` tools appear in your tool list**: tell157 them "The Power Automate tools are connected" and move on.158- **If they're missing**: the MCP server isn't registered. Fix it automatically:159160 1. **Locate the installed plugin's MCP bundle.** This only matches a bundle161 inside a `power-automate` plugin directory, so it can't pick up another162 plugin's MCP server:163 ```bash164 node -e "const fs=require('fs'),p=require('path'),d=p.join(process.env.HOME||process.env.USERPROFILE,'.copilot','installed-plugins');const find=(dir)=>{let out=[];for(const e of fs.readdirSync(dir,{withFileTypes:true})){const f=p.join(dir,e.name);if(e.isDirectory()){try{out=out.concat(find(f))}catch{}}else if(e.name==='mcp.mjs'&&p.basename(p.dirname(dir))==='power-automate'){out.push(dir)}}return out};try{const hits=find(d);if(hits.length===1)console.log(JSON.stringify({found:true,serverDir:hits[0],mcpMjs:p.join(hits[0],'mcp.mjs')}));else if(hits.length>1)console.log(JSON.stringify({found:false,reason:'multiple power-automate bundles',candidates:hits}));else console.log(JSON.stringify({found:false}))}catch(e){console.log(JSON.stringify({found:false,error:e.message}))}"165 ```166 If it reports `multiple power-automate bundles`, show the candidates and ask167 the user which one to register rather than guessing.168169 2. **If exactly one was found**, read `~/.copilot/mcp-config.json`, add the170 `flowagent` MCP entry, and write it back:171 ```bash172 node -e "const fs=require('fs'),p=require('path');const home=process.env.HOME||process.env.USERPROFILE;const cfgPath=p.join(home,'.copilot','mcp-config.json');let cfg;try{cfg=JSON.parse(fs.readFileSync(cfgPath,'utf8'))}catch{cfg={mcpServers:{}}};if(!cfg.mcpServers)cfg.mcpServers={};if(cfg.mcpServers.flowagent){console.log('already registered');process.exit(0)}const d=p.join(home,'.copilot','installed-plugins');const find=(dir)=>{let out=[];for(const e of fs.readdirSync(dir,{withFileTypes:true})){const f=p.join(dir,e.name);if(e.isDirectory()){try{out=out.concat(find(f))}catch{}}else if(e.name==='mcp.mjs'&&p.basename(p.dirname(dir))==='power-automate'){out.push(dir)}}return out};const hits=find(d);if(hits.length!==1){console.log(hits.length?'ambiguous: '+JSON.stringify(hits):'mcp.mjs not found');process.exit(1)}const mcpPath=p.join(hits[0],'mcp.mjs');cfg.mcpServers.flowagent={command:'node',args:[mcpPath]};fs.writeFileSync(cfgPath,JSON.stringify(cfg,null,2)+'\n');console.log('registered flowagent MCP at '+mcpPath)"173 ```174175 3. **Tell the user** to restart the agent (Copilot CLI: `/restart`, Claude Code:176 restart the process). After restart, `flowagent-*` tools should appear.177178 4. **If not found** (plugin not installed at all): tell them to install the179 plugin first:180 ```181 /plugin marketplace add microsoft/power-platform-skills182 ```183 Then select `power-automate` and run `/setup` again.184185## Step 5: Smoke Test186187Verify everything works end-to-end by listing the user's environments:188189- **Preferred**: call the `list_environments` tool.190- **If MCP tools aren't available**: run `node <path-to-plugin>/server/mcp.mjs`191 to confirm the bundled MCP server starts cleanly, then fix the plugin install192 or `.mcp.json` wiring before retrying.193194- **If it returns environments**: Success! Tell them:195 - "Everything is working! Here are your Power Automate environments:"196 - Show the environments in a simple table (name, location).197 - If there are multiple, ask which one they mainly use and suggest setting it198 as the default (the `set_current_env` tool, or ask "set my default199 environment to <name>").200 - Tell them about the available skills:201 - **`/browse-flows`** — Browse your flows202 - **`/create-flow`** — Create a new flow203 - **`/debug-flow`** — Fix a broken flow204- **If it fails**: Check the error. Common issues:205 - Auth error → go back to Step 3206 - Tools not found → go back to Step 4207 - Network error → ask if they're behind a corporate proxy/VPN208209## Tone Guidelines210211- Use "we" language: "Let's check if Node.js is installed"212- Celebrate small wins: "Great, Node.js is ready!"213- Don't dump all steps at once — do one at a time and confirm before moving on214- If something fails, don't panic — explain what went wrong in plain English and what to do215- Never show raw JSON errors to the user without explaining what they mean