[FEATURE] Multi-account session management
@HasanAboShally ya está trabajando en esto.
Desde el 12/4/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Problem
Consultants and developers who work across multiple Microsoft Fabric tenants and client environments face a painful workflow today: every time they need to switch context, they must run fab auth logout followed by a full fab auth login, re-authenticating interactively each time.
Real-world use case
A typical consulting scenario:
- Client A - Production tenant
tenant-aaa, user[email protected] - Client B - Dev/test tenant
tenant-bbb, user[email protected] - Internal - Corporate tenant
tenant-ccc, user[email protected]
Switching between these today requires a full logout/login cycle for each transition, which is disruptive, slow, and breaks automation scripts that assume a persistent session.
Proposed solution
Add stored user session management to the CLI so that multiple interactive authentication sessions can coexist and be switched instantly:
| Command | Description |
|---|---|
fab auth list |
List all stored user sessions with active/valid status |
fab auth switch |
Switch to another stored session (interactive or direct) |
fab auth switch -u <account> -t <tenant> |
Switch directly to a specific account (case-insensitive) |
fab auth logout -u <account> |
Log out a specific session without affecting others |
fab auth logout --all |
Clear all stored sessions |
Behavior
- Two stored sessions, no flags:
fab auth switchautomatically toggles to the other account. - Three or more sessions, no flags: an interactive prompt is shown.
- With
-u(and optionally-t): switches directly, no prompt. - Sessions are validated against the MSAL token cache and marked as valid/invalid in
fab auth list. - Environment variable authentication (
FAB_TOKEN, etc.) takes precedence and blocks session switching with a clear error message. - Interactive login now preserves the broker-backed MSAL app across the Fabric, OneLake, and Azure token warm-up so newly selected accounts are stored cleanly on Windows.
Acceptance criteria
-
fab auth listshows all stored sessions with active/valid/last_used metadata -
fab auth switchsupports direct (-u,-t) and interactive selection -
fab auth logoutsupports per-session removal (-u,-t) and bulk (--all) - Username matching is case-insensitive
- Session switching is blocked when env var auth is active
- Documentation and examples are up to date
- Tests cover happy paths and edge cases
- Lenguaje dominante
- Python
- Estrellas
- 173
- Forks
- 63
- Merge medio
- 3 d 2 h
- PR fusionados (30 d)
- 4
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/fabric-cli
-
ai:bug-triage:unable-to-process bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
microsoft/fabric-cli#287 · 2 comentarios ·
-
ai:feature-triage:unable-to-process enhancement
Dificultad 3/5 1-2 días Aptitud para principiantes 64/100
microsoft/fabric-cli#292 · 1 comentario ·
-
ai:question-triage:unable-to-process question
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
microsoft/fabric-cli#288 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
microsoft/fabric-cli#286 · 3 comentarios ·
-
ai:feature-triage:unable-to-process enhancement
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
microsoft/fabric-cli#279 · 1 comentario ·
Todos los issues de microsoft/fabric-cli
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
kornia/kornia#5263 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Metadata correction for W16-5400Abiertoapproved correction metadata
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
acl-org/acl-anthology#10133 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
BasedHardware/omi#20084 ·
Los mantenedores suelen responder en 1 día
-
bug needs-acceptance wg/evaluation-quality
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
vllm-project/semantic-router#4424 ·
Los mantenedores suelen responder en 1 día