Your accounts and access#

Before you start technical work, set up your accounts and access. If something is missing — reach out to your onboarding buddy or IT.

Account checklist#

• Microsoft 365 / Entra ID — @professnet.pl email, Teams, OneDrive. Turn on MFA right away (the next lesson is about security).
• Azure — access to subscriptions according to your role (usually via an Entra group). Sign in with az login.
• GitHub — an account added to the Professnet organization. Set up an SSH key or gh auth login.
• Tools — Visual Studio / VS Code, Git, Node.js, Python, Docker.

Quick verification in the terminal#

az account show          # are you signed in to Azure?
gh auth status           # access to GitHub / the Professnet organization?
git config user.email    # is the @professnet.pl email set?
node -v && python3 -V     # developer environments

The principle of least privilege#

You get only the permissions you need for your role. This is not a lack of trust — it is the ISO 27001 standard and protection against mistakes. If you need more, ask with a justification.

Tip: never share your credentials. Each person has their own account — that way the audit knows who did what.

Secrets and passwords#

• Keep passwords and tokens in a (company) password manager, never in the code.
• API keys and connection strings → Key Vault / GitHub Secrets, not in the repo.
• Lost a token? Report it immediately — we rotate, we don't hide.

---

Once your accounts are working, move on — we'll show you how best to use this training platform.