Lab 00: Set up your workstation

At a glance

Time: About 45 minutes
Level: intro
Platforms: Windows 11, macOS
Copilot surfaces: VS Code, Copilot CLI, github.com, Power BI Desktop
You'll use: setup, prerequisites, copilot-cli
Starts from: None needed
Ends at: None needed
Last verified: Not yet run end to end on Windows 11

Works on macOS

Nobody has run this lab end to end on Windows 11 yet. The steps follow the current docs for each tool, but menu labels may differ. The verify command at the end is the source of truth, and feedback is welcome.

Why this matters

The rest of the lab moves fast. Agents will run PowerShell scripts, read TMDL files, start MCP servers, open Power BI Desktop, and use GitHub features. This page gets the machine ready without hiding any installs behind an automation script. You run each installer yourself, then the repo check in Lab 01 tells you what still needs attention.

Concepts

Power BI Desktop: the Windows app that opens the PBIP project. You need it for Desktop and MCP labs. See Lab 02.
PowerShell 7: the shell used by every lab script. Windows PowerShell 5.1 is not enough.
GitHub Copilot agent mode: the VS Code chat mode where Copilot can use tools, edit files, and run commands after you approve them.
Copilot CLI: the terminal surface used in Lab 11.
Organization policy: a GitHub Business or Enterprise admin switch that can allow or block MCP, custom agents, code review, and cloud agent.

Before you begin

Use a Windows 11 machine for the full lab. macOS works for file-based labs, but Power BI Desktop does not run there.
Sign in to Windows with an account that can install applications, or know how to request them from IT.
Have a GitHub account with Copilot enabled. Labs 12 and 13 need paid plan features.
Don’t clone the repo yet. That happens in Lab 01.

Steps

Press Windows+R.
Type winver and press Enter.
Confirm the dialog says Windows 11, version 23H2 or later.

You should see: an OS version you can support for the whole track. On Windows, note the version in case you need to open a help desk ticket.

I finished step 1

Step 2. Install PowerShell 7

Run the installer yourself. Nothing on this page installs automatically.

Windows
macOS

winget install --id Microsoft.PowerShell --source winget
pwsh -NoLogo -NoProfile -Command "$PSVersionTable.PSVersion"

# Install PowerShell 7 from the official package, or use your approved package manager.
pwsh -NoLogo -NoProfile -Command '$PSVersionTable.PSVersion'

You should see: version 7.4 or later. The prompt or terminal title should say pwsh, not Windows PowerShell.

    } catch {
        return $null
    }
    if ($text -match $Pattern) { return [version] $Matches[1] }
    return [version] '0.0'
}

# PowerShell
$ps = $PSVersionTable.PSVersion

View scripts/Test-Prerequisites.ps1 on GitHub

I finished step 2

Step 3. Install Git and enable long paths

Windows
macOS

winget install --id Git.Git --source winget
git --version
git config --global core.longpaths true
git config --global --get core.longpaths

# Install Git from git-scm.com, Xcode Command Line Tools, or your approved package manager.
git --version

Leave line endings to the repo’s .gitattributes. Don’t set a global autocrlf rule just for this lab.

You should see: Git 2.40 or later. On Windows, the final command prints true.

I finished step 3

Step 4. Install Python 3.12

Windows
macOS

winget install --id Python.Python.3.12 --source winget
py -3.12 --version
python --version

If python opens the Microsoft Store instead of printing a version, turn off the Store aliases under Settings > Apps > Advanced app settings > App execution aliases.

# Install Python 3.12 or later from python.org or your approved package manager.
python3 --version

You should see: Python 3.12 or later. In Lab 01, the repo script creates .venv from this install.

I finished step 4

Step 5. Install Node.js 20 or later

Node is used by the local lab site and by MCP servers launched with npx.

Windows
macOS

winget install --id OpenJS.NodeJS.LTS --source winget
node --version
npm --version

# Install the current Node.js LTS from nodejs.org or your approved package manager.
node --version
npm --version

You should see: Node.js v20 or later and an npm version. Reopen your terminal if the command isn’t found after install.

I finished step 5

Step 6. Install VS Code and sign in to Copilot

Windows
macOS

winget install --id Microsoft.VisualStudioCode --source winget
code --version

# Install VS Code from code.visualstudio.com.
code --version

Then configure the UI:

Open VS Code.
Open the Command Palette: Ctrl+Shift+P (macOS: Cmd+Shift+P), or View > Command Palette.
Run Shell Command: Install ‘code’ command in PATH if code --version failed.
Select Accounts in the Activity Bar, then Sign in to Sync Settings or Sign in with GitHub.
Open Copilot Chat: Ctrl+Alt+I (macOS: Ctrl+Cmd+I), or View > Chat.
Confirm the mode menu in the chat input includes Agent or Agent mode.

You should see: VS Code on PATH, Copilot Chat opens, and your GitHub account is signed in.

I finished step 6

Step 7. Install Power BI Desktop and enable project previews

Windows only Preview feature

winget install --id Microsoft.PowerBI --source winget

If your company blocks winget or the Store, use your managed software catalog and ask for Power BI Desktop, not the Power BI service.

After install:

Open Power BI Desktop.
Go to File > Options and settings > Options > Preview features.
Enable Power BI Project (.pbip) save option if it appears.
Enable Store semantic model using TMDL format if it appears.
Select OK, close Desktop, and reopen it.

| `ai-prep/` | Markdown and YAML | Drafts of AI instructions, synonyms, and verified answers (added in Lab 09). |

## Open it

Power BI Desktop runs on Windows only. On Windows 11:

1. Run `pwsh ./scripts/Set-LocalDataLink.ps1` once so `C:\ContosoPharmacyDemo\data\` points at `data/generated/`.
2. In Power BI Desktop, turn on the preview features **Power BI Project (.pbip) save option** and **Store semantic model using TMDL format** (File > Options and settings > Options > Preview features), then restart Desktop.

View fabric/README.md on GitHub

You should see: Power BI Desktop starts, and the PBIP and TMDL preview options are either enabled or absent because your Desktop version has them on by default.

I finished step 7

Step 8. Install GitHub CLI and Copilot CLI

GitHub CLI is optional until Labs 12 and 13. Copilot CLI is used in Lab 11.

Windows
macOS

winget install --id GitHub.cli --source winget
gh --version
npm install -g @github/copilot
copilot --version

# Install GitHub CLI with the official installer or your approved package manager.
gh --version
npm install -g @github/copilot
copilot --version

Then sign in:

gh auth login
copilot

You should see: gh auth login completes for GitHub.com, and copilot starts an authenticated CLI session or prints a sign-in URL.

I finished step 8

Step 9. Check your Copilot plan and organization policies

Needs a paid Copilot plan

Open GitHub in a browser.
Go to Settings > Copilot for your personal account, or ask your organization owner to check Organization settings > Copilot > Policies.
Confirm these features are allowed for this repo or organization:
- Copilot Chat in VS Code.
- Agent mode in the IDE.
- Custom agents, prompt files, and instructions.
- MCP servers in Copilot.
- Copilot CLI.
- Copilot code review for Lab 12.
- Copilot cloud agent for Lab 13.
If you’re on Copilot Business or Enterprise, ask whether policy, firewall, or data loss prevention rules block MCP servers, hooks, or package downloads.

You should see: enough access for your chosen track. If your admin won’t enable code review or cloud agent, you can still finish the Core track through Lab 11.

I finished step 9

Verify your work

You can’t run the automated check yet, because it lives in the repo you clone in Lab 01. After cloning, run this from the repo root. It calls scripts/Test-Prerequisites.ps1, which checks PowerShell, Git, Python, VS Code, Power BI Desktop on Windows, Node.js, GitHub CLI, and Copilot CLI.

Run this from the repo root in a PowerShell 7 terminal (Terminal > New Terminal in VS Code):

Windows
macOS

pwsh ./scripts/lab/Test-LabProgress.ps1 -Lab 00

pwsh ./scripts/lab/Test-LabProgress.ps1 -Lab 00

Checks marked Windows only print SKIP on macOS. SKIP doesn't count as a failure.

When everything is done you should see:

PASS  L00-pwsh         PowerShell 7.4 or later
PASS  L00-git          Git 2.40+ with core.longpaths on Windows
PASS  L00-python       Python 3.12 or later
PASS  L00-node         Node.js 20 or later
PASS  L00-vscode       VS Code on PATH
PASS  L00-desktop      Power BI Desktop installed
PASS  L00-gh           GitHub CLI (optional, used in Labs 12 and 13)
PASS  L00-copilot-cli  Copilot CLI (used in Lab 11)

Lab 00: 8 of 8 checks passed.

Each FAIL line prints a hint and a link back to the step on this page that fixes it. The command exits with code 0 when every required check passes.

Check	What it looks at	If it fails
`L00-pwsh`	PowerShell 7.4 or later	Install PowerShell 7 with winget install Microsoft.PowerShell, then open a new terminal. Go to step 2
`L00-git`	Git 2.40+ with core.longpaths on Windows	Install Git for Windows, then run git config --global core.longpaths true. Go to step 3
`L00-python`	Python 3.12 or later	Install Python 3.12+ (winget install Python.Python.3.12) and reopen the terminal. Go to step 4
`L00-node`	Node.js 20 or later	Install Node.js LTS (winget install OpenJS.NodeJS.LTS). Go to step 5
`L00-vscode`	VS Code on PATH	Install VS Code and enable 'Add to PATH'. Go to step 6
`L00-desktop` (Windows only)	Power BI Desktop installed	Install Power BI Desktop from the Microsoft Store or the download center. Go to step 7
`L00-gh` (optional)	GitHub CLI (optional, used in Labs 12 and 13)	winget install GitHub.cli, then gh auth login. Go to step 8
`L00-copilot-cli` (optional)	Copilot CLI (used in Lab 11)	npm install -g @github/copilot, then run copilot once to sign in. Go to step 8

Optional checks can FAIL without failing the lab.

Troubleshooting

winget isn’t recognized

Install App Installer from the Microsoft Store, use your company’s software catalog, or download the official installer from the product site. On managed devices, winget may be disabled by policy.

PowerShell still opens as Windows PowerShell 5.1

Open PowerShell 7 from the Start menu, or set your terminal profile to PowerShell 7 under Windows Terminal > Settings > Startup > Default profile. The command must be pwsh, not powershell.

python opens the Microsoft Store

Turn off the Store aliases under Settings > Apps > Advanced app settings > App execution aliases. Then open a new terminal and run py -3.12 --version.

Copilot Chat opens, but Agent mode is missing

Update VS Code, sign in again, and confirm your Copilot plan allows agents. In organizations, an admin may need to enable agent mode or related Copilot policy settings.

Power BI Desktop preview settings are missing

Preview names move between Desktop versions. If the PBIP or TMDL options are missing, try opening the PBIP in Lab 02. If it opens as a project with TMDL files, your Desktop version already has the feature enabled.

Knowledge check

Why does this lab use PowerShell 7 instead of Windows PowerShell 5.1?The scripts use PowerShell 7 behavior and run the same way on Windows and macOS.Power BI Desktop can only be launched from PowerShell 7.Git refuses to clone PBIP files from Windows PowerShell 5.1.

Show the answer

The scripts use PowerShell 7 behavior and run the same way on Windows and macOS.

The scripts declare PowerShell 7 and use cross-platform behavior. Desktop is Windows only, but the scripts themselves also run under pwsh on macOS.

Which step actually installs system software?The VerifyStep component installs missing tools.Only the commands you run yourself install software.Initialize-DevEnvironment.ps1 installs Git, Python, and VS Code.

Show the answer

Only the commands you run yourself install software.

The repo scripts install Python packages inside .venv, but they do not install system tools. You run winget or official installers yourself.

Which features should a Business or Enterprise admin check before Labs 12 and 13?Only GitHub Pages.Copilot code review and Copilot cloud agent policies.Only Dependabot alerts.

Show the answer

Copilot code review and Copilot cloud agent policies.

Labs 12 and 13 use paid Copilot features that can also be blocked by org policy. Check them before you need them.

Recap and next

You installed the tools the lab expects, signed in to Copilot, enabled Power BI Desktop project support, and checked the policies that can block later labs. Next you create your own copy of the repo and run the real prerequisite check.

Next: Lab 01: Get your copy and explore the repo

Go further

Save the installed versions in a note so you can compare them if a menu moves later.
If you’re on a corporate device, open the help desk ticket now for Power BI Desktop, Copilot policy, MCP servers, winget, and package downloads.

Something wrong or unclear on this page? Open a lab feedback issue. The form is prefilled with this page's name. Nothing is sent until you submit it, and please don't include screenshots of real accounts.