docs(phase-10): complete phase execution and verification

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
docs(10-03): complete branding-data-foundation plan 03
2026-04-08 13:30:23 +02:00 · 2026-04-08 12:37:15 +02:00 · 2026-04-08 12:36:12 +02:00 · 2026-04-08 12:33:57 +02:00 · 2026-04-08 12:33:33 +02:00 · 2026-04-08 12:32:23 +02:00
609 changed files with 10641 additions and 1023 deletions
@@ -0,0 +1,79 @@
+---
+phase: 10
+title: Branding Data Foundation
+status: ready-for-planning
+created: 2026-04-08
+---
+
+# Phase 10 Context: Branding Data Foundation
+
+## Decided Areas (from prior research + STATE.md)
+
+These are locked — do not re-litigate during planning or execution.
+
+| Decision | Value |
+|---|---|
+| Logo storage format | Base64 strings in JSON (not file paths) |
+| MSP logo location | `BrandingSettings.cs` model → `branding.json` |
+| Client logo location | On `TenantProfile` model (per-tenant) |
+| File path after import | Discarded — only base64 persists |
+| SVG support | Rejected (XSS risk) — PNG/JPG only |
+| User directory service | New `GraphUserDirectoryService`, separate from `GraphUserSearchService` |
+| Directory auto-load | No — explicit "Load Directory" button required |
+| New NuGet packages | None — existing stack covers everything |
+| Export service signature | Optional `ReportBranding? branding = null` parameter on existing export methods |
+
+## Discussed Areas
+
+### 1. Logo Metadata Model
+
+**Decision:** Store base64 + MIME type as separate fields in a shared `LogoData` record.
+
+- Shared model: `LogoData { string Base64, string MimeType }` — used by both MSP logo (in `BrandingSettings`) and client logo (on `TenantProfile`)
+- `MimeType` is `"image/png"` or `"image/jpeg"`, determined at import time from magic bytes
+- No other metadata stored — no original filename, dimensions, or import date
+- Export services concatenate `data:{MimeType};base64,{Base64}` for HTML `<img>` tags
+- WPF preview converts `Base64` bytes to `BitmapImage` directly
+
+### 2. Logo Validation & Compression
+
+**Decision:** Validate format via magic bytes, auto-compress oversized files silently.
+
+- **Format detection:** Read file header magic bytes only — ignore file extension entirely
+  - PNG signature: `89 50 4E 47` (first 4 bytes)
+  - JPEG signature: `FF D8 FF` (first 3 bytes)
+  - Anything else → reject with specific error message (e.g., "File format is BMP, only PNG and JPG are accepted")
+- **Size handling:** If file exceeds 512 KB, auto-compress silently (no user notification)
+  - Strategy: resize dimensions (e.g., max 300px width/height) + reduce quality
+  - Keep original format — PNG stays PNG, JPEG stays JPEG (no format conversion)
+  - Compress until under 512 KB
+- **Dimension limits:** None — the 512 KB cap and compression handle naturally
+- **Validation errors:** Specific messages for format rejection (format-related only, since size is auto-handled)
+
+### 3. Profile Deletion & Duplication Behavior
+
+**Decision:** Warn about logo loss on deletion; do NOT copy logo on duplication.
+
+- **Deletion:** When deleting a tenant profile that has a client logo, the confirmation message explicitly mentions it: "This will also remove its client logo." The logo is embedded in the profile JSON, so deletion is automatic — no orphaned files.
+- **Duplication:** Duplicating a tenant profile copies connection fields (Name, TenantUrl, ClientId) but starts with a blank client logo. The user must re-import or auto-pull for the new profile. Rationale: duplicated profiles are typically for different tenants, so the logo shouldn't carry over.
+
+## Deferred Ideas (out of scope for Phase 10)
+
+- Logo preview in Settings UI (Phase 12)
+- Auto-pull client logo from Entra branding API (Phase 11/12)
+- Report header layout with logos side-by-side (Phase 11)
+- "Load Directory" button placement decision (Phase 14)
+- Session-scoped directory cache (UDIR-F01, deferred)
+
+## code_context
+
+| Asset | Path | Reuse |
+|---|---|---|
+| TenantProfile model | `SharepointToolbox/Core/Models/TenantProfile.cs` | Extend with `LogoData? ClientLogo` property |
+| AppSettings model | `SharepointToolbox/Core/Models/AppSettings.cs` | Reference for BrandingSettings pattern |
+| SettingsRepository | `SharepointToolbox/Infrastructure/Persistence/SettingsRepository.cs` | Clone pattern for BrandingRepository (write-then-replace + SemaphoreSlim) |
+| ProfileRepository | `SharepointToolbox/Infrastructure/Persistence/ProfileRepository.cs` | Already handles TenantProfile persistence — will serialize new logo field |
+| GraphUserSearchService | `SharepointToolbox/Services/GraphUserSearchService.cs` | Reference for Graph SDK usage, auth, and query patterns |
+| GraphClientFactory | `SharepointToolbox/Infrastructure/Auth/GraphClientFactory.cs` | Provides `GraphServiceClient` for new directory service |
+| DI registration | `SharepointToolbox/App.xaml.cs` (lines 73-163) | Register new BrandingRepository, BrandingService, GraphUserDirectoryService |
+| Profile deletion UI | `SharepointToolbox/ViewModels/ProfileManagementViewModel.cs` | Update deletion confirmation message to mention logo |
@@ -8,10 +8,18 @@ A C#/WPF desktop application for IT administrators and MSPs to audit and manage

 Administrators can audit and manage SharePoint/Teams permissions and storage across multiple client tenants from a single, reliable desktop application.

+## Current Milestone: v2.2 Report Branding & User Directory
+
+**Goal:** Add customizable logos to HTML reports and a full user directory browse mode in the user access audit tab.
+
+**Target features:**
+- HTML report branding with MSP logo (global) and client logo (per tenant — pull from tenant or import)
+- User directory browse mode as alternative to search in user access audit tab
+
 ## Current State

 **Shipped:** v1.1 Enhanced Reports (2026-04-08)
-**Status:** Feature-complete for v1.1; no active milestone
+**Status:** Active milestone v2.2

 **v1.1 shipped features:**
 - Global multi-site selection in toolbar (pick sites once, all tabs use them)
@@ -40,6 +48,11 @@ Distribution: 200 MB self-contained EXE (win-x64)
 - [x] Simplified permissions reports (plain language, summary views) (SIMP-01/02/03) — v1.1
 - [x] Storage metrics graph by file type (pie/donut and bar chart, toggleable) (VIZZ-01/02/03) — v1.1

+### Active
+
+- [ ] HTML report branding with MSP logo (global) and client logo (per tenant)
+- [ ] User directory browse mode in user access audit tab
+
 ### Out of Scope

 - Cross-platform support (Mac/Linux) — WPF is Windows-only; not justified for current user base
@@ -80,4 +93,4 @@ Distribution: 200 MB self-contained EXE (win-x64)
 | Wave 0 scaffold pattern | Models + interfaces + test stubs before implementation | ✓ Good — all phases had test targets from day 1 |

 ---
-*Last updated: 2026-04-08 after v1.1 milestone shipped*
+*Last updated: 2026-04-08 after v2.2 milestone started*
@@ -0,0 +1,73 @@
+# Requirements: SharePoint Toolbox v2.2
+
+**Defined:** 2026-04-08
+**Core Value:** Administrators can audit and manage SharePoint/Teams permissions and storage across multiple client tenants from a single, reliable desktop application.
+
+## v2.2 Requirements
+
+Requirements for v2.2 Report Branding & User Directory. Each maps to roadmap phases.
+
+### Report Branding
+
+- [x] **BRAND-01**: User can import an MSP logo in application settings (global, persisted across sessions)
+- [ ] **BRAND-02**: User can preview the imported MSP logo in settings UI
+- [x] **BRAND-03**: User can import a client logo per tenant profile
+- [ ] **BRAND-04**: User can auto-pull client logo from tenant's Entra branding API
+- [ ] **BRAND-05**: All five HTML report types display MSP and client logos in a consistent header
+- [x] **BRAND-06**: Logo import validates format (PNG/JPG) and enforces 512 KB size limit
+
+### User Directory
+
+- [ ] **UDIR-01**: User can toggle between search mode and directory browse mode in user access audit tab
+- [ ] **UDIR-02**: User can browse full tenant user directory with pagination (handles 999+ users)
+- [ ] **UDIR-03**: User can filter directory by user type (member vs guest)
+- [ ] **UDIR-04**: User can see department and job title columns in directory list
+- [ ] **UDIR-05**: User can select one or more users from directory to run the access audit
+
+## Future Requirements
+
+### Report Branding (Deferred)
+
+- **BRAND-F01**: PDF export with embedded logos
+- **BRAND-F02**: Custom report title/footer text per tenant
+
+### User Directory (Deferred)
+
+- **UDIR-F01**: Session-scoped directory cache (avoid re-fetching on tab switch)
+- **UDIR-F02**: Export user directory list to CSV
+
+## Out of Scope
+
+| Feature | Reason |
+|---------|--------|
+| CSV report branding | CSV is data-only format; logos don't apply |
+| Logo in application title bar | Not a report branding concern; separate UX decision |
+| User directory as standalone tab | Directory browse is a mode within existing user access audit tab |
+| Real-time directory sync | One-time load with manual refresh is sufficient for audit workflows |
+
+## Traceability
+
+Which phases cover which requirements. Updated during roadmap creation.
+
+| Requirement | Phase | Status |
+|-------------|-------|--------|
+| BRAND-01 | Phase 10 | Complete |
+| BRAND-03 | Phase 10 | Complete |
+| BRAND-06 | Phase 10 | Complete |
+| BRAND-05 | Phase 11 | Pending |
+| BRAND-04 | Phase 11 | Pending |
+| BRAND-02 | Phase 12 | Pending |
+| UDIR-01 | Phase 13 | Pending |
+| UDIR-02 | Phase 13 | Pending |
+| UDIR-03 | Phase 13 | Pending |
+| UDIR-04 | Phase 13 | Pending |
+| UDIR-05 | Phase 14 | Pending |
+
+**Coverage:**
+- v2.2 requirements: 11 total
+- Mapped to phases: 11
+- Unmapped: 0
+
+---
+*Requirements defined: 2026-04-08*
+*Last updated: 2026-04-08 after roadmap creation — all 11 requirements mapped to Phases 10-14*
@@ -4,6 +4,7 @@

 - ✅ **v1.0 MVP** — Phases 1-5 (shipped 2026-04-07) — [archive](milestones/v1.0-ROADMAP.md)
 - ✅ **v1.1 Enhanced Reports** — Phases 6-9 (shipped 2026-04-08) — [archive](milestones/v1.1-ROADMAP.md)
+- 🔄 **v2.2 Report Branding & User Directory** — Phases 10-14 (active)

 ## Phases

@@ -28,9 +29,84 @@

 </details>

+### v2.2 Report Branding & User Directory (Phases 10-14)
+
+- [x] **Phase 10: Branding Data Foundation** — Models, repository, and services for logo storage and user directory enumeration (completed 2026-04-08)
+- [ ] **Phase 11: HTML Export Branding + ViewModel Integration** — Inject logos into all 5 HTML report types; wire branding into export-triggering ViewModels and logo management commands
+- [ ] **Phase 12: Branding UI Views** — Settings and profile dialog logo sections with live preview; auto-pull client logo from Entra branding API
+- [ ] **Phase 13: User Directory ViewModel** — Browse mode state, paginated directory load, member/guest filter, and department/job title columns
+- [ ] **Phase 14: User Directory View** — Toggle panel in UserAccessAuditView, user selection to trigger existing audit pipeline
+
+## Phase Details
+
+### Phase 10: Branding Data Foundation
+**Goal**: The application can store, validate, and retrieve MSP and client logos as portable base64 strings in JSON, and can enumerate a full tenant user list with pagination.
+**Depends on**: Nothing (additive to existing infrastructure)
+**Requirements**: BRAND-01, BRAND-03, BRAND-06
+**Success Criteria** (what must be TRUE):
+  1. An MSP logo imported as a PNG or JPG file is persisted as a base64 string in `branding.json` and survives an application restart
+  2. A client logo imported per tenant profile is persisted as a base64 string inside the tenant's profile JSON and is not affected by other tenants' profiles
+  3. A file larger than 512 KB or not a valid PNG/JPG is rejected at import time with an error; no invalid data reaches the JSON store
+  4. `GraphUserDirectoryService.GetUsersAsync` returns all enabled member users for a tenant, following `@odata.nextLink` until exhausted, without truncating at 999
+**Plans**: 3 plans
+Plans:
+- [ ] 10-01-PLAN.md — Logo models, BrandingRepository, BrandingService with validation/compression
+- [ ] 10-02-PLAN.md — GraphUserDirectoryService with PageIterator pagination
+- [ ] 10-03-PLAN.md — DI registration in App.xaml.cs and full test suite gate
+
+### Phase 11: HTML Export Branding + ViewModel Integration
+**Goal**: All five HTML reports display MSP and client logos in a consistent header, and administrators can manage logos from Settings and the profile dialog without touching the View layer.
+**Depends on**: Phase 10
+**Requirements**: BRAND-05, BRAND-04
+**Success Criteria** (what must be TRUE):
+  1. Running any of the five HTML exports (Permissions, Storage, Search, Duplicates, User Access) produces an HTML file whose header contains the MSP logo `<img>` tag when an MSP logo is configured
+  2. When a client logo is configured for the active tenant, the same HTML export header contains both the MSP logo and the client logo side by side
+  3. When no logo is configured, the HTML export header contains no broken image placeholder and the report renders identically to the pre-branding output
+  4. SettingsViewModel exposes browse/clear commands for MSP logo; ProfileManagementViewModel exposes browse/clear commands for client logo — both commands are exercisable without opening any View
+  5. Auto-pulling the client logo from the tenant's Entra branding API stores the logo in the tenant profile and falls back silently when no Entra branding is configured
+**Plans**: TBD
+
+### Phase 12: Branding UI Views
+**Goal**: Administrators can see, import, preview, and clear logos directly in the Settings and profile management dialogs.
+**Depends on**: Phase 11
+**Requirements**: BRAND-02, BRAND-04 (view layer for Entra pull)
+**Success Criteria** (what must be TRUE):
+  1. Opening Settings shows the MSP logo section: an import button, a live thumbnail preview of the current logo, and a clear button that removes the logo immediately
+  2. Opening a tenant profile dialog shows the client logo section with the same import/preview/clear controls
+  3. Importing a logo via the UI shows the thumbnail preview without requiring an application restart
+  4. Clicking "Pull from Entra" in the profile dialog fetches and displays the tenant's banner logo if one exists, and shows a clear user-facing message if none is configured
+**Plans**: TBD
+
+### Phase 13: User Directory ViewModel
+**Goal**: The UserAccessAuditViewModel supports a full directory browse mode with paginated load, member/guest filtering, and department/job title display, fully testable without the View.
+**Depends on**: Phase 10
+**Requirements**: UDIR-01, UDIR-02, UDIR-03, UDIR-04
+**Success Criteria** (what must be TRUE):
+  1. `UserAccessAuditViewModel` exposes a toggle property that switches between Search mode (existing people-picker behavior) and Browse mode (directory list behavior), with no regression to Search mode behavior
+  2. Invoking the load-directory command fetches all enabled member users via `PageIterator`, updates a progress observable with the running user count, and supports cancellation mid-load
+  3. A "Members only / Include guests" toggle filters the displayed list in-memory without issuing a new Graph request
+  4. Each user row in the observable collection exposes DisplayName, UPN, Department, and JobTitle; Department and JobTitle columns are visible and sortable in the ViewModel's `ICollectionView`
+**Plans**: TBD
+
+### Phase 14: User Directory View
+**Goal**: Administrators can toggle into directory browse mode from the user access audit tab, see the paginated user list with filters, and launch an access audit for a selected user.
+**Depends on**: Phase 13
+**Requirements**: UDIR-05, UDIR-01 (view layer)
+**Success Criteria** (what must be TRUE):
+  1. The user access audit tab shows a mode toggle control (e.g., radio buttons or segmented control) that visibly switches the left panel between the existing people-picker and the directory browse panel
+  2. In browse mode, selecting a user from the directory list and clicking Run Audit (or equivalent) launches the existing audit pipeline for that user, producing the same results as if the user had been found via search
+  3. While the directory is loading, the panel shows a "Loading... X users" counter and an active cancel button; the load button is disabled to prevent concurrent requests
+  4. When the directory load is cancelled or fails, the panel returns to a ready state with a clear status message and no broken UI
+**Plans**: TBD
+
 ## Progress

 | Phase | Milestone | Plans | Status | Completed |
 |-------|-----------|-------|--------|-----------|
 | 1-5 | v1.0 | 36/36 | Shipped | 2026-04-07 |
 | 6-9 | v1.1 | 25/25 | Shipped | 2026-04-08 |
+| 10. Branding Data Foundation | 3/3 | Complete    | 2026-04-08 | — |
+| 11. HTML Export Branding + ViewModel Integration | v2.2 | 0/? | Not started | — |
+| 12. Branding UI Views | v2.2 | 0/? | Not started | — |
+| 13. User Directory ViewModel | v2.2 | 0/? | Not started | — |
+| 14. User Directory View | v2.2 | 0/? | Not started | — |
@@ -1,124 +1,70 @@
 ---
 gsd_state_version: 1.0
-milestone: v1.1
-milestone_name: v1.1 Enhanced Reports
-status: shipped
-stopped_at: Milestone archived
-last_updated: "2026-04-08T00:00:00Z"
-last_activity: 2026-04-08 — v1.1 milestone archived and tagged
+milestone: v2.2
+milestone_name: Report Branding & User Directory
+status: planning
+stopped_at: Completed 10-branding-data-foundation/10-03-PLAN.md
+last_updated: "2026-04-08T10:40:19.677Z"
+last_activity: 2026-04-08 — Roadmap created for v2.2
 progress:
-  total_phases: 4
-  completed_phases: 4
-  total_plans: 25
-  completed_plans: 25
+  total_phases: 5
+  completed_phases: 1
+  total_plans: 3
+  completed_plans: 3
 ---

 # Project State

 ## Project Reference

-See: .planning/PROJECT.md (updated 2026-04-07)
+See: .planning/PROJECT.md (updated 2026-04-08)

 **Core value:** Administrators can audit and manage SharePoint/Teams permissions and storage across multiple client tenants from a single, reliable desktop application.
-**Current focus:** v1.1 Enhanced Reports — global site selection, user access audit, simplified permissions, storage visualization
+**Current focus:** v2.2 Report Branding & User Directory — HTML report logos (Phases 10-12), user directory browse mode (Phases 13-14)

 ## Current Position

-Phase: 9 — Storage Visualization
-Plan: 4 of 4
-Status: Plan 09-04 complete — StorageViewModel chart unit tests
-Last activity: 2026-04-07 — Completed 09-04 (StorageViewModel chart unit tests)
+Phase: 10 (not started)
+Plan: —
+Status: Roadmap ready — awaiting phase planning
+Last activity: 2026-04-08 — Roadmap created for v2.2

 ```
-v1.1 Progress: [██████████] 100%
-Phase 6 [x] → Phase 7 [x] → Phase 8 [x] → Phase 9 [x]
+v2.2 Progress: [░░░░░░░░░░] 0% (0/5 phases)
 ```

-## Performance Metrics
-
-| Metric | v1.0 | v1.1 (running) |
-|--------|------|----------------|
-| Phases | 5 | 4 planned |
-| Plans | 36 | TBD |
-| Commits | 164 | 0 |
-| Tests | 134 pass / 22 skip | — |
-| Phase 06-global-site-selection P02 | 8 | 1 tasks | 1 files |
-| Phase 06-global-site-selection P01 | 2 | 2 tasks | 3 files |
-| Phase 06-global-site-selection P03 | 2 | 3 tasks | 5 files |
-| Phase 06-global-site-selection P04 | 2 | 3 tasks | 6 files |
-| Phase 06-global-site-selection P05 | 2 | 1 tasks | 1 files |
-| Phase 07-user-access-audit P01 | 5 | 2 tasks | 3 files |
-| Phase 07-user-access-audit P03 | 2 | 1 tasks | 1 files |
-| Phase 07-user-access-audit P02 | 1 | 1 tasks | 1 files |
-| Phase 07-user-access-audit P06 | 2 | 2 tasks | 2 files |
-| Phase 07-user-access-audit P04 | 2 | 1 tasks | 1 files |
-| Phase 07-user-access-audit P05 | 4 | 2 tasks | 2 files |
-| Phase 07-user-access-audit P07 | 8 | 3 tasks | 7 files |
-| Phase 07-user-access-audit P08 | 2 | 2 tasks | 4 files |
-| Phase 07-user-access-audit P09 | 6 | 1 tasks | 1 files |
-| Phase 07-user-access-audit P10 | 5 | 1 tasks | 1 files |
-| Phase 08 P02 | 84 | 1 tasks | 1 files |
-| Phase 08 P03 | 77 | 1 tasks | 2 files |
-| Phase 08 P04 | 2 | 2 tasks | 2 files |
-| Phase 08 P05 | 2 | 2 tasks | 4 files |
-| Phase 08 P06 | 2 | 2 tasks | 3 files |
-| Phase 09 P01 | 1 | 2 tasks | 3 files |
-| Phase 09 P02 | 1 | 1 tasks | 1 files |
-| Phase 09 P03 | 573 | 2 tasks | 5 files |
-| Phase 09 P04 | 146 | 1 tasks | 2 files |
-
 ## Accumulated Context

 ### Decisions

 Decisions are logged in PROJECT.md Key Decisions table.

-**v1.1 architectural notes:**
- Global site selection (Phase 6) changes the toolbar; all tabs must bind to a shared `GlobalSiteSelectionViewModel` or equivalent. Use `WeakReferenceMessenger` for cross-tab site-changed notifications, consistent with v1.0 messenger usage.
- Per-tab override (SITE-02) means each `FeatureViewModelBase` subclass stores a nullable local site override; null means "use global".
- Storage Visualization (Phase 9) requires a WPF charting NuGet (LiveCharts2 recommended — actively maintained, WPF-native, self-contained friendly). Wire chart data binding to the existing storage scan result model.
- Self-contained EXE constraint: charting library must not require runtime DLLs outside the publish output.
- [Phase 06-02]: MainWindowViewModel uses Func<Window>? factory for SitePickerDialog and broadcasts GlobalSitesChangedMessage via WeakReferenceMessenger on collection change
- [Phase 06-01]: GlobalSitesChangedMessage uses IReadOnlyList<SiteInfo> (snapshot, not ObservableCollection) so receivers cannot mutate sender state
- [Phase 06-01]: FeatureViewModelBase.OnGlobalSitesReceived (private) updates GlobalSites then calls OnGlobalSitesChanged (protected virtual) — separates storage from derived class hooks
- [Phase 06-03]: Added using SharepointToolbox.Core.Models to MainWindow.xaml.cs for TenantProfile in SitePickerDialog factory lambda
- [Phase 06-03]: toolbar.selectSites.tooltipDisabled added to resources but not wired in XAML — WPF Button disabled tooltip requires style trigger (deferred)
- [Phase 06-global-site-selection]: PermissionsViewModel uses _hasLocalSiteOverride guard for SelectedSites; site picker sets flag, tenant switch resets it
- [Phase 06-global-site-selection]: Single-site VMs use partial void OnSiteUrlChanged to detect local typing; clearing field reverts to global
- [Phase 06-global-site-selection]: BulkMembersViewModel confirmed excluded: no SiteUrl field, CSV-driven per-row site URLs
- [Phase 06-global-site-selection]: Test 8 asserts override-reset via next global sites message (not SiteUrl='' — OnSiteUrlChanged re-applies global immediately when cleared)
- [Phase 06-global-site-selection]: Used reflection to set _hasLocalSiteOverride in PermissionsViewModel test — avoids needing a real SitePickerDialog
- [Phase 07-01]: UserAccessEntry is fully denormalized (one row = one user + one object + one permission) for direct DataGrid binding
- [Phase 07-01]: IsHighPrivilege and IsExternalUser pre-computed at scan time; GraphUserResult co-located with IGraphUserSearchService interface
- [Phase 07-03]: Minimum 2-character query guard prevents overly broad Graph API requests
- [Phase 07-03]: OData single-quote escaping (replace apostrophe with two apostrophes) prevents injection in startsWith filter
- [Phase 07-03]: ConsistencyLevel=eventual and Count=true both required for startsWith on Graph directory objects
- [Phase 07-user-access-audit]: TenantProfile.ClientId empty in service — session pre-authenticated at ViewModel level; SessionManager returns cached context by URL key
- [Phase 07-user-access-audit]: Bidirectional contains matching for user login — handles both plain email and full SharePoint claim formats
- [Phase 07-user-access-audit]: UserAccessCsvExportService has two write modes: WriteAsync (per-user files to directory) and WriteSingleFileAsync (combined for SaveFileDialog)
- [Phase 07-user-access-audit]: HTML sortTable() scoped per group so sorting in by-user view keeps each user's rows together
- [Phase 07-04]: CollectionViewSource bound at construction; ApplyGrouping() swaps PropertyGroupDescription between UserLogin/SiteUrl on IsGroupByUser toggle
- [Phase 07-04]: ExportCsvAsync uses WriteSingleFileAsync (combined file) not WriteAsync (per-user directory) to match SaveFileDialog single-path UX
- [Phase 07-05]: Autocomplete ListBox visibility managed via code-behind CollectionChanged — WPF DataTrigger cannot compare to non-zero Count without converter
- [Phase 07-05]: Simple ListBox autocomplete (not Popup) following plan's recommended simpler alternative — avoids Popup placement issues
- [Phase 07-user-access-audit]: Dialog factory wiring in MainWindow.xaml.cs by casting auditView.DataContext to UserAccessAuditViewModel — matches PermissionsView pattern
- [Phase 07-user-access-audit]: UserAccessAuditView created inline (Rule 3) when 07-05 found missing — follows 07-05 spec with two-panel layout
- [Phase 07-user-access-audit]: Used internal TestRunOperationAsync for ViewModel tests; Application.Current null in tests lets else branch run synchronously
- [Phase 07-user-access-audit]: WeakReferenceMessenger.Default.Reset() in test constructor prevents cross-test contamination from message registrations
- [Phase 07-09]: Guest badge (orange pill) and warning icon (⚠) use DataTrigger-driven Visibility on DataGridTemplateColumn cells — collapsed by default, visible only when IsExternalUser/IsHighPrivilege=True
- [Phase 07-10]: Extended CreateViewModel to 3-tuple (vm, auditMock, graphMock) so debounce test can verify SearchUsersAsync calls
- [Phase 08]: ActiveItemsSource returns Results or SimplifiedResults based on IsSimplifiedMode -- View binds to single property
- [Phase 08]: InvertBoolConverter in Core/Converters namespace for reuse; summary cards use WrapPanel; row color triggers only match SimplifiedPermissionEntry
- [Phase 08]: FR translations use XML entities for accented chars matching existing resx convention
- [Phase 09-01]: LiveChartsCore.SkiaSharpView.WPF 2.0.0-rc5.4 added as charting library; SkiaSharp backend for self-contained EXE compatibility
- [Phase 09-01]: FileTypeMetric record uses Extension (with dot), TotalSizeBytes (long), FileCount (int), DisplayLabel (computed) matching existing model patterns
- [Phase 09-01]: CollectFileTypeMetricsAsync omits StorageScanOptions since file-type scan covers all non-hidden libraries without folder depth filtering
- [Phase 09-02]: Added System.IO using explicitly -- WPF project implicit usings do not include System.IO for Path.GetExtension
- [Phase 09]: Used wrapper Grid elements with MultiDataTrigger for LiveCharts2 chart visibility -- more reliable than styling third-party controls directly
+**v2.2 architectural decisions (locked at roadmap):**
+- Logos stored as base64 strings in JSON (not file paths). `BrandingSettings.cs` holds MSP logo; `TenantProfile` holds client logo. File path is discarded after import. This decision is locked — all downstream phases depend on it.
+- Client logo lives on `TenantProfile`, NOT in `BrandingSettings`. Per-tenant ownership; prevents serialization and deletion awkwardness.
+- Export services use optional `ReportBranding? branding = null` parameter. All existing call sites compile unchanged. No new `IHtmlExportService` interface needed.
+- `GraphUserDirectoryService` is a new service, separate from `GraphUserSearchService`. Different pagination model (`PageIterator`), different cancellation needs.
+- Directory does NOT load automatically on tab open. Explicit "Load Directory" button required to avoid blocking UI on large tenants.
+- SVG logo support: rejected. XSS risk in data-URIs. PNG/JPG only.
+- No new NuGet packages for v2.2. All capabilities provided by existing stack (BCL, Microsoft.Graph 5.74.0, WPF PresentationCore).
+
+**v1.1 architectural notes (carried forward):**
+- Global site selection (Phase 6) changes the toolbar; all tabs bind to shared `GlobalSiteSelectionViewModel`. `WeakReferenceMessenger` for cross-tab site-changed notifications.
+- Per-tab override (SITE-02): each `FeatureViewModelBase` subclass stores a nullable local site override; null means "use global".
+- Storage Visualization (Phase 9): LiveCharts2, WPF-native, self-contained friendly.
+- [Phase 10-branding-data-foundation]: No ConsistencyLevel header on equality filter for GetUsersAsync (unlike GraphUserSearchService startsWith which requires it)
+- [Phase 10-branding-data-foundation]: MapUser extracted as internal static in GraphUserDirectoryService for direct unit testability without live Graph endpoint
+- [Phase 10-branding-data-foundation]: Type alias AppGraphClientFactory used in GraphUserDirectoryService to disambiguate from Microsoft.Graph.GraphClientFactory
+- [Phase 10-branding-data-foundation]: Used WPF PresentationCore (BitmapDecoder/TransformedBitmap/JpegBitmapEncoder) for image compression instead of System.Drawing.Bitmap — System.Drawing.Common is not available without a new NuGet package on .NET 10, and WPF PresentationCore is already in the stack
+- [Phase 10-branding-data-foundation]: LogoData is a non-positional record with init properties (not positional constructor) to avoid System.Text.Json deserialization failure
+- [Phase 10-branding-data-foundation]: No new using statements required for Phase 10 DI registrations — SharepointToolbox.Infrastructure.Persistence and SharepointToolbox.Services were already imported

 ### Pending Todos

-1. Add global multi-site selection option (ui) — `todos/pending/2026-04-07-add-global-multi-site-selection-option.md` — **addressed by Phase 6**
+- Confirm `$filter=accountEnabled eq true and userType eq 'Member'` behavior without `ConsistencyLevel: eventual` against a real tenant before Phase 13 planning.
+- Verify Entra `bannerLogo` stream endpoint returns empty body (not HTTP 404) when no tenant branding is configured — determines error handling branch for BRAND-04 auto-pull.
+- Decide report header layout before Phase 11: logos side-by-side (current spec: `display: flex; gap: 16px`, MSP left + client right).
+- Decide "Load Directory" button placement before Phase 14: inside browse panel (recommended) or tab-level toolbar.

 ### Blockers/Concerns

@@ -126,6 +72,7 @@ None.

 ## Session Continuity

-Last session: 2026-04-07T13:40:30Z
-Stopped at: Completed 09-04-PLAN.md
+Last session: 2026-04-08T10:36:58.959Z
+Stopped at: Completed 10-branding-data-foundation/10-03-PLAN.md
 Resume file: None
+Next step: `/gsd:plan-phase 10`
@@ -0,0 +1,131 @@
+# Phase 6: Global Site Selection - Context
+
+**Gathered:** 2026-04-07
+**Status:** Ready for planning
+
+<domain>
+## Phase Boundary
+
+Administrators can select one or more target sites once from the toolbar and have every feature tab use that selection by default — eliminating the need to re-enter site URLs on each tab. Individual tabs can override the global selection without clearing the global state.
+
+Requirements: SITE-01, SITE-02
+
+Success Criteria:
+1. A multi-site picker control is visible in the main toolbar at all times, regardless of which tab is active
+2. Selecting sites in the toolbar causes all feature tabs to default to those sites when an operation is run
+3. A user can override the global selection on any individual tab without clearing the global state
+4. The global site selection persists across tab switches within the same session
+
+</domain>
+
+<decisions>
+## Implementation Decisions
+
+### Toolbar site picker placement
+- Add a "Select Sites" button to the existing ToolBar (after the Clear Session button, separated by a Separator)
+- Next to the button, show a summary label: "3 site(s) selected" or "No sites selected"
+- Clicking the button opens the existing SitePickerDialog pattern (reuse from PermissionsViewModel)
+- The picker requires a connected tenant (button disabled when no profile is connected)
+
+### Global selection broadcast
+- Create a new `GlobalSitesChangedMessage` (ValueChangedMessage<IReadOnlyList<SiteInfo>>) sent via WeakReferenceMessenger when the toolbar selection changes
+- `MainWindowViewModel` owns the global site selection state: `ObservableCollection<SiteInfo> GlobalSelectedSites`
+- On tenant switch, clear the global selection (sites belong to a tenant)
+
+### Tab consumption of global selection
+- `FeatureViewModelBase` registers for `GlobalSitesChangedMessage` in `OnActivated()` and stores the global sites in a protected property `IReadOnlyList<SiteInfo> GlobalSites`
+- Each tab's `RunOperationAsync` checks: if local override sites exist, use those; else if GlobalSites is non-empty, use those; else fall back to the SiteUrl text box
+- The SiteUrl TextBox on each tab shows a placeholder/hint when global sites are active (e.g., "Using 3 globally selected sites" as watermark text)
+
+### Local override behavior
+- Tabs that already have per-tab site pickers (like Permissions) keep them
+- When a user picks sites locally on a tab, that overrides the global selection for that tab only
+- A "Clear local selection" action resets the tab back to using global sites
+- The global selection in the toolbar is never modified by per-tab overrides
+
+### Tabs that DO NOT consume global sites
+- Settings tab: no site URL needed
+- Bulk Sites tab: creates sites from CSV, does not target existing sites
+- Templates tab (apply): creates a new site, does not target existing sites
+
+### Tabs that consume global sites (single-site)
+- Storage, Search, Duplicates, Folder Structure: these currently take a single SiteUrl
+- When global sites are selected, these tabs use the first site in the global list by default
+- The SiteUrl TextBox is pre-filled with the first global site URL (user can change it = local override)
+
+### Tabs that consume global sites (multi-site)
+- Permissions: already supports multi-site; global sites pre-populate its SelectedSites collection
+- Transfer: source site pre-filled from first global site
+
+### Claude's Discretion
+- Exact XAML layout of the toolbar site picker button and label
+- Whether to refactor SitePickerDialog or reuse as-is from MainWindow code-behind
+- Internal naming of properties and helper methods
+- Whether to add a chip/tag display for selected sites or keep it as a count label
+- Localization key names for new strings
+
+</decisions>
+
+<code_context>
+## Existing Code Insights
+
+### Reusable Assets
+- `SitePickerDialog` (Views/Dialogs/): Filterable checkbox list of sites with Select All/Deselect All — loads from `ISiteListService.GetSitesAsync()`. Currently only wired from PermissionsView; needs to be wired from MainWindow toolbar too.
+- `SiteInfo(string Url, string Title)` record (Core/Models/): Already used by SitePickerDialog and PermissionsViewModel
+- `ISiteListService.GetSitesAsync(TenantProfile, progress, ct)`: Enumerates all sites in a tenant. Already registered in DI.
+- `TenantSwitchedMessage`: Broadcast pattern for tenant changes — global site selection follows the same pattern
+- `WeakReferenceMessenger`: Already used for TenantSwitched and ProgressUpdated messages
+- `FeatureViewModelBase.OnActivated()`: Already registers for TenantSwitchedMessage — extend to also register for GlobalSitesChangedMessage
+
+### Established Patterns
+- Dialog factories set on ViewModels as `Func<Window>?` from View code-behind (keeps Window refs out of VMs)
+- `[ObservableProperty]` for bindable state
+- `ObservableCollection<T>` for list-bound UI elements
+- Tab content resolved from DI in MainWindow.xaml.cs
+- Localization via `TranslationSource.Instance["key"]` with Strings.resx / Strings.fr.resx
+
+### Integration Points
+- `MainWindow.xaml`: Add site picker button + label to ToolBar
+- `MainWindowViewModel.cs`: Add GlobalSelectedSites, OpenGlobalSitePickerCommand, GlobalSitesChangedMessage broadcast
+- `MainWindow.xaml.cs`: Wire SitePickerDialog factory for the toolbar (same pattern as PermissionsView)
+- `FeatureViewModelBase.cs`: Register for GlobalSitesChangedMessage, add GlobalSites property
+- `Core/Messages/`: New GlobalSitesChangedMessage class
+- Each tab ViewModel: Update RunOperationAsync to check GlobalSites before falling back to SiteUrl
+- `Strings.resx` / `Strings.fr.resx`: New localization keys for toolbar site picker
+- `App.xaml.cs`: No new DI registrations needed (SitePickerDialog factory and ISiteListService already registered)
+
+### Key Files
+| File | Role |
+|------|------|
+| `MainWindow.xaml` | Toolbar XAML — add site picker controls |
+| `MainWindowViewModel.cs` | Global selection state + command |
+| `MainWindow.xaml.cs` | Wire SitePickerDialog factory for toolbar |
+| `FeatureViewModelBase.cs` | Base class — receive global sites message |
+| `Core/Messages/TenantSwitchedMessage.cs` | Pattern reference for new message |
+| `Views/Dialogs/SitePickerDialog.xaml.cs` | Reuse as-is |
+| `ViewModels/Tabs/PermissionsViewModel.cs` | Already has multi-site pattern — adapt to consume global sites |
+| `ViewModels/Tabs/StorageViewModel.cs` | Single-site pattern — adapt to consume global sites |
+
+</code_context>
+
+<specifics>
+## Specific Ideas
+
+- The toolbar site count label should update live when sites are selected/deselected
+- When no tenant is connected, the "Select Sites" button should be disabled with a tooltip explaining why
+- Clearing the session (Clear Session button) should also clear the global site selection
+- The global selection should survive tab switching (it lives on MainWindowViewModel, not on any tab)
+
+</specifics>
+
+<deferred>
+## Deferred Ideas
+
+None — all items are within phase scope
+
+</deferred>
+
+---
+
+*Phase: 06-global-site-selection*
+*Context gathered: 2026-04-07*
@@ -0,0 +1,163 @@
+---
+phase: 07-user-access-audit
+plan: 09
+type: execute
+wave: 6
+depends_on: ["07-05"]
+files_modified:
+  - SharepointToolbox/Views/Tabs/UserAccessAuditView.xaml
+autonomous: true
+requirements:
+  - UACC-01
+  - UACC-02
+gap_closure: true
+source_gaps:
+  - "Gap 1: Missing DataGrid visual indicators (guest badge + warning icon)"
+  - "Gap 2: Missing ObjectType column in DataGrid"
+must_haves:
+  truths:
+    - "High-privilege entries show a warning icon (⚠) in the Permission Level column cell template"
+    - "External users show a guest badge (👤 Guest) in the User column cell template when IsExternalUser is true"
+    - "DataGrid columns include Object Type bound to ObjectType between Object and Permission Level"
+  artifacts:
+    - path: "SharepointToolbox/Views/Tabs/UserAccessAuditView.xaml"
+      provides: "DataGrid with visual indicators for high-privilege/external users and ObjectType column"
+      contains: "IsExternalUser DataTrigger, IsHighPrivilege warning icon, ObjectType column"
+  key_links:
+    - from: "SharepointToolbox/Views/Tabs/UserAccessAuditView.xaml"
+      to: "SharepointToolbox/Core/Models/UserAccessEntry.cs"
+      via: "Bindings on IsExternalUser, IsHighPrivilege, ObjectType properties"
+      pattern: "DataTrigger Binding"
+---
+
+<objective>
+Add missing visual indicators and ObjectType column to the UserAccessAuditView DataGrid.
+
+Purpose: Close verification gaps 1 and 2 — the XAML currently lacks per-row guest badges for external users, warning icons for high-privilege entries, and the ObjectType column.
+Output: Updated UserAccessAuditView.xaml with all three additions.
+</objective>
+
+<execution_context>
+@C:/Users/dev/.claude/get-shit-done/workflows/execute-plan.md
+@C:/Users/dev/.claude/get-shit-done/templates/summary.md
+</execution_context>
+
+<context>
+@.planning/PROJECT.md
+@.planning/ROADMAP.md
+@.planning/phases/07-user-access-audit/07-CONTEXT.md
+@.planning/phases/07-user-access-audit/07-05-SUMMARY.md
+@.planning/phases/07-user-access-audit/07-VERIFICATION.md
+
+<interfaces>
+<!-- UserAccessEntry fields available for binding -->
+From SharepointToolbox/Core/Models/UserAccessEntry.cs:
+```csharp
+public record UserAccessEntry(
+    string UserDisplayName, string UserLogin,
+    string SiteUrl, string SiteTitle,
+    string ObjectType, string ObjectTitle, string ObjectUrl,
+    string PermissionLevel, AccessType AccessType, string GrantedThrough,
+    bool IsHighPrivilege, bool IsExternalUser);
+```
+
+<!-- Current DataGrid columns (lines 219-249 of UserAccessAuditView.xaml) -->
+Current columns: User (UserLogin), Site (SiteTitle), Object (ObjectTitle), Permission Level (PermissionLevel), Access Type (template), Granted Through (GrantedThrough).
+Missing: ObjectType column, guest badge in User column, warning icon in Permission Level column.
+</interfaces>
+</context>
+
+<tasks>
+
+<task type="auto">
+  <name>Task 1: Add guest badge, warning icon, and ObjectType column to DataGrid</name>
+  <files>SharepointToolbox/Views/Tabs/UserAccessAuditView.xaml</files>
+  <action>
+    Modify the DataGrid columns section (lines 219-249) with three changes:
+
+    **Change 1 — Convert User column to DataGridTemplateColumn with guest badge:**
+    Replace the plain `DataGridTextColumn Header="User"` with a `DataGridTemplateColumn`:
+    ```xml
+    <DataGridTemplateColumn Header="User" Width="180">
+      <DataGridTemplateColumn.CellTemplate>
+        <DataTemplate>
+          <StackPanel Orientation="Horizontal">
+            <TextBlock Text="{Binding UserLogin}" VerticalAlignment="Center" />
+            <Border Background="#F39C12" CornerRadius="3" Padding="4,1" Margin="6,0,0,0"
+                    VerticalAlignment="Center">
+              <Border.Style>
+                <Style TargetType="Border">
+                  <Setter Property="Visibility" Value="Collapsed" />
+                  <Style.Triggers>
+                    <DataTrigger Binding="{Binding IsExternalUser}" Value="True">
+                      <Setter Property="Visibility" Value="Visible" />
+                    </DataTrigger>
+                  </Style.Triggers>
+                </Style>
+              </Border.Style>
+              <TextBlock Text="Guest" FontSize="10" Foreground="White" FontWeight="SemiBold" />
+            </Border>
+          </StackPanel>
+        </DataTemplate>
+      </DataGridTemplateColumn.CellTemplate>
+    </DataGridTemplateColumn>
+    ```
+
+    **Change 2 — Convert Permission Level column to DataGridTemplateColumn with warning icon:**
+    Replace the plain `DataGridTextColumn Header="Permission Level"` with a `DataGridTemplateColumn`:
+    ```xml
+    <DataGridTemplateColumn Header="Permission Level" Width="140">
+      <DataGridTemplateColumn.CellTemplate>
+        <DataTemplate>
+          <StackPanel Orientation="Horizontal">
+            <TextBlock Text="⚠" Foreground="#E74C3C" Margin="0,0,4,0"
+                       FontSize="12" VerticalAlignment="Center">
+              <TextBlock.Style>
+                <Style TargetType="TextBlock">
+                  <Setter Property="Visibility" Value="Collapsed" />
+                  <Style.Triggers>
+                    <DataTrigger Binding="{Binding IsHighPrivilege}" Value="True">
+                      <Setter Property="Visibility" Value="Visible" />
+                    </DataTrigger>
+                  </Style.Triggers>
+                </Style>
+              </TextBlock.Style>
+            </TextBlock>
+            <TextBlock Text="{Binding PermissionLevel}" VerticalAlignment="Center" />
+          </StackPanel>
+        </DataTemplate>
+      </DataGridTemplateColumn.CellTemplate>
+    </DataGridTemplateColumn>
+    ```
+
+    **Change 3 — Add ObjectType column between Object and Permission Level:**
+    ```xml
+    <DataGridTextColumn Header="Object Type" Binding="{Binding ObjectType}" Width="90" />
+    ```
+
+    Insert this column after the "Object" column and before the "Permission Level" column.
+
+    Final column order: User (with guest badge), Site, Object, Object Type, Permission Level (with ⚠ icon), Access Type, Granted Through.
+  </action>
+  <verify>
+    <automated>cd "C:\Users\dev\Documents\projets\Sharepoint" && dotnet build SharepointToolbox/SharepointToolbox.csproj --no-restore 2>&1 | tail -5</automated>
+  </verify>
+  <done>DataGrid now shows: guest badge on external user rows (orange "Guest" pill), warning icon (⚠) on high-privilege permission levels, and ObjectType column showing Site Collection/Site/List/Folder distinction.</done>
+</task>
+
+</tasks>
+
+<verification>
+- `dotnet build SharepointToolbox/SharepointToolbox.csproj` — XAML compiles without errors
+- Visual inspection: DataGrid columns order is User (with guest badge), Site, Object, Object Type, Permission Level (with ⚠), Access Type, Granted Through
+- Guest badge visible only when IsExternalUser=true
+- Warning icon visible only when IsHighPrivilege=true
+</verification>
+
+<success_criteria>
+The DataGrid shows guest badges for external users, warning icons for high-privilege entries, and the ObjectType column — closing verification gaps 1 and 2.
+</success_criteria>
+
+<output>
+After completion, create `.planning/phases/07-user-access-audit/07-09-SUMMARY.md`
+</output>
@@ -0,0 +1,171 @@
+---
+phase: 07-user-access-audit
+plan: 10
+type: execute
+wave: 6
+depends_on: ["07-08"]
+files_modified:
+  - SharepointToolbox.Tests/ViewModels/UserAccessAuditViewModelTests.cs
+autonomous: true
+requirements:
+  - UACC-01
+gap_closure: true
+source_gaps:
+  - "Gap 3: Debounced search test absent (Plan 08 truth partially unmet)"
+must_haves:
+  truths:
+    - "A unit test verifies that setting SearchQuery to a value of length >= 2 triggers IGraphUserSearchService.SearchUsersAsync after the debounce delay"
+  artifacts:
+    - path: "SharepointToolbox.Tests/ViewModels/UserAccessAuditViewModelTests.cs"
+      provides: "Debounced search unit test"
+      contains: "SearchQuery_debounced_calls_SearchUsersAsync"
+  key_links:
+    - from: "SharepointToolbox.Tests/ViewModels/UserAccessAuditViewModelTests.cs"
+      to: "SharepointToolbox/ViewModels/Tabs/UserAccessAuditViewModel.cs"
+      via: "Tests SearchQuery property change → DebounceSearchAsync → SearchUsersAsync"
+      pattern: "SearchUsersAsync"
+---
+
+<objective>
+Add a unit test for the debounced search path in UserAccessAuditViewModel.
+
+Purpose: Close verification gap 3 — plan 08 required "ViewModel tests verify: debounced search triggers service" but no such test exists.
+Output: One new test method added to UserAccessAuditViewModelTests.cs.
+</objective>
+
+<execution_context>
+@C:/Users/dev/.claude/get-shit-done/workflows/execute-plan.md
+@C:/Users/dev/.claude/get-shit-done/templates/summary.md
+</execution_context>
+
+<context>
+@.planning/PROJECT.md
+@.planning/ROADMAP.md
+@.planning/phases/07-user-access-audit/07-CONTEXT.md
+@.planning/phases/07-user-access-audit/07-08-SUMMARY.md
+@.planning/phases/07-user-access-audit/07-VERIFICATION.md
+
+<interfaces>
+<!-- ViewModel debounce path (from UserAccessAuditViewModel.cs) -->
+```csharp
+// Line 281-290: OnSearchQueryChanged triggers DebounceSearchAsync
+partial void OnSearchQueryChanged(string value)
+{
+    _searchCts?.Cancel();
+    _searchCts?.Dispose();
+    _searchCts = new CancellationTokenSource();
+    var ct = _searchCts.Token;
+    _ = DebounceSearchAsync(value, ct);
+}
+
+// Line 406-458: DebounceSearchAsync waits 300ms then calls SearchUsersAsync
+private async Task DebounceSearchAsync(string query, CancellationToken ct)
+{
+    await Task.Delay(300, ct);
+    // ... guard: query null/whitespace or < 2 chars → clear and return
+    var clientId = _currentProfile?.ClientId ?? string.Empty;
+    var results = await _graphUserSearchService.SearchUsersAsync(clientId, query, 10, ct);
+    // ... dispatches results to SearchResults collection
+}
+```
+
+<!-- Existing test patterns (from UserAccessAuditViewModelTests.cs) -->
+```csharp
+// Uses Moq + xUnit. CreateViewModel helper returns (vm, auditMock).
+// mockGraph is Mock<IGraphUserSearchService> created inside CreateViewModel.
+// The test needs access to mockGraph — may need to extend CreateViewModel to return it.
+```
+
+<!-- IGraphUserSearchService contract -->
+```csharp
+public interface IGraphUserSearchService
+{
+    Task<IReadOnlyList<GraphUserResult>> SearchUsersAsync(
+        string clientId, string query, int maxResults, CancellationToken ct);
+}
+```
+</interfaces>
+</context>
+
+<tasks>
+
+<task type="auto">
+  <name>Task 1: Add debounced search unit test</name>
+  <files>SharepointToolbox.Tests/ViewModels/UserAccessAuditViewModelTests.cs</files>
+  <action>
+    **Step 1**: Extend the `CreateViewModel` helper to also return the `Mock<IGraphUserSearchService>` so tests can set up expectations and verify calls on it. Change the return tuple from `(vm, auditMock)` to `(vm, auditMock, graphMock)`. Update all 8 existing test calls to destructure the third element (use `_` discard).
+
+    **Step 2**: Add the following test method after Test 8:
+
+    ```csharp
+    // ── Test 9: Debounced search triggers SearchUsersAsync ──────────────
+
+    [Fact]
+    public async Task SearchQuery_debounced_calls_SearchUsersAsync()
+    {
+        var graphResults = new List<GraphUserResult>
+        {
+            new("Alice Smith", "alice@contoso.com", "alice@contoso.com")
+        };
+
+        var (vm, _, graphMock) = CreateViewModel();
+
+        graphMock
+            .Setup(s => s.SearchUsersAsync(
+                It.IsAny<string>(),
+                It.Is<string>(q => q == "Ali"),
+                It.IsAny<int>(),
+                It.IsAny<CancellationToken>()))
+            .ReturnsAsync(graphResults);
+
+        // Set a TenantProfile so _currentProfile is non-null
+        var profile = new TenantProfile
+        {
+            Name = "Test",
+            TenantUrl = "https://contoso.sharepoint.com",
+            ClientId = "test-client-id"
+        };
+        WeakReferenceMessenger.Default.Send(new TenantSwitchedMessage(profile));
+
+        // Act: set SearchQuery which triggers OnSearchQueryChanged → DebounceSearchAsync
+        vm.SearchQuery = "Ali";
+
+        // Wait longer than 300ms debounce to allow async fire-and-forget to complete
+        await Task.Delay(600);
+
+        // Assert: SearchUsersAsync was called with the query
+        graphMock.Verify(
+            s => s.SearchUsersAsync(
+                It.IsAny<string>(),
+                "Ali",
+                It.IsAny<int>(),
+                It.IsAny<CancellationToken>()),
+            Times.Once);
+    }
+    ```
+
+    **Important notes:**
+    - The `DebounceSearchAsync` method uses `Application.Current?.Dispatcher` which will be null in tests. The else branch (lines 438-442) handles this by adding directly to SearchResults — this is the test-safe path.
+    - The 600ms delay in the test ensures the 300ms debounce + async execution has time to complete.
+    - The TenantSwitchedMessage sets `_currentProfile` so that `_currentProfile?.ClientId` is non-null.
+  </action>
+  <verify>
+    <automated>cd "C:\Users\dev\Documents\projets\Sharepoint" && dotnet test SharepointToolbox.Tests/SharepointToolbox.Tests.csproj --filter "FullyQualifiedName~UserAccessAuditViewModelTests" 2>&1 | tail -10</automated>
+  </verify>
+  <done>Debounced search test passes: setting SearchQuery to "Ali" triggers SearchUsersAsync after the 300ms debounce. All 9 ViewModel tests pass with no regressions.</done>
+</task>
+
+</tasks>
+
+<verification>
+- `dotnet test SharepointToolbox.Tests/SharepointToolbox.Tests.csproj --filter "FullyQualifiedName~UserAccessAuditViewModelTests"` — all 9 tests pass
+- `dotnet test SharepointToolbox.Tests/SharepointToolbox.Tests.csproj` — no regressions
+</verification>
+
+<success_criteria>
+The debounced search path (SearchQuery → 300ms delay → SearchUsersAsync) has unit test coverage, closing verification gap 3.
+</success_criteria>
+
+<output>
+After completion, create `.planning/phases/07-user-access-audit/07-10-SUMMARY.md`
+</output>
@@ -0,0 +1,274 @@
+---
+phase: 10-branding-data-foundation
+plan: 01
+type: execute
+wave: 1
+depends_on: []
+files_modified:
+  - SharepointToolbox/Core/Models/LogoData.cs
+  - SharepointToolbox/Core/Models/BrandingSettings.cs
+  - SharepointToolbox/Core/Models/TenantProfile.cs
+  - SharepointToolbox/Infrastructure/Persistence/BrandingRepository.cs
+  - SharepointToolbox/Services/IBrandingService.cs
+  - SharepointToolbox/Services/BrandingService.cs
+  - SharepointToolbox.Tests/Services/BrandingServiceTests.cs
+  - SharepointToolbox.Tests/Services/BrandingRepositoryTests.cs
+autonomous: true
+requirements:
+  - BRAND-01
+  - BRAND-03
+  - BRAND-06
+
+must_haves:
+  truths:
+    - "An MSP logo imported as PNG or JPG is persisted as base64 in branding.json and survives round-trip"
+    - "A client logo imported per tenant profile is persisted as base64 inside the profile JSON"
+    - "A file that is not PNG/JPG (e.g., BMP) is rejected with a descriptive error message"
+    - "A file larger than 512 KB is silently compressed to fit under the limit"
+    - "A file under 512 KB is stored without modification"
+  artifacts:
+    - path: "SharepointToolbox/Core/Models/LogoData.cs"
+      provides: "Shared logo record with Base64 and MimeType properties"
+      contains: "record LogoData"
+    - path: "SharepointToolbox/Core/Models/BrandingSettings.cs"
+      provides: "MSP logo wrapper model"
+      contains: "LogoData? MspLogo"
+    - path: "SharepointToolbox/Core/Models/TenantProfile.cs"
+      provides: "Client logo property on existing profile model"
+      contains: "LogoData? ClientLogo"
+    - path: "SharepointToolbox/Infrastructure/Persistence/BrandingRepository.cs"
+      provides: "JSON persistence for BrandingSettings with write-then-replace"
+      contains: "SemaphoreSlim"
+    - path: "SharepointToolbox/Services/BrandingService.cs"
+      provides: "Logo import with magic byte validation and auto-compression"
+      exports: ["ImportLogoAsync"]
+    - path: "SharepointToolbox.Tests/Services/BrandingServiceTests.cs"
+      provides: "Unit tests for validation, compression, rejection"
+      min_lines: 60
+    - path: "SharepointToolbox.Tests/Services/BrandingRepositoryTests.cs"
+      provides: "Unit tests for repository round-trip"
+      min_lines: 30
+  key_links:
+    - from: "SharepointToolbox/Services/BrandingService.cs"
+      to: "SharepointToolbox/Infrastructure/Persistence/BrandingRepository.cs"
+      via: "constructor injection"
+      pattern: "BrandingRepository"
+    - from: "SharepointToolbox/Services/BrandingService.cs"
+      to: "SharepointToolbox/Core/Models/LogoData.cs"
+      via: "return type"
+      pattern: "LogoData"
+    - from: "SharepointToolbox/Core/Models/BrandingSettings.cs"
+      to: "SharepointToolbox/Core/Models/LogoData.cs"
+      via: "property type"
+      pattern: "LogoData\\? MspLogo"
+    - from: "SharepointToolbox/Core/Models/TenantProfile.cs"
+      to: "SharepointToolbox/Core/Models/LogoData.cs"
+      via: "property type"
+      pattern: "LogoData\\? ClientLogo"
+---
+
+<objective>
+Create the logo storage infrastructure: models, repository, and branding service with validation/compression.
+
+Purpose: BRAND-01, BRAND-03, BRAND-06 require models for logo data, a repository for MSP branding persistence, extension of TenantProfile for client logos, and a service that validates format (magic bytes) and auto-compresses oversized files.
+
+Output: LogoData record, BrandingSettings model, TenantProfile extension, BrandingRepository, BrandingService (with IBrandingService interface), and comprehensive unit tests.
+</objective>
+
+<execution_context>
+@C:/Users/dev/.claude/get-shit-done/workflows/execute-plan.md
+@C:/Users/dev/.claude/get-shit-done/templates/summary.md
+</execution_context>
+
+<context>
+@.planning/PROJECT.md
+@.planning/ROADMAP.md
+@.planning/STATE.md
+@.planning/phases/10-branding-data-foundation/10-RESEARCH.md
+
+<interfaces>
+<!-- Existing patterns the executor needs to follow exactly. -->
+
+From SharepointToolbox/Core/Models/AppSettings.cs:
+```csharp
+namespace SharepointToolbox.Core.Models;
+
+public class AppSettings
+{
+    public string DataFolder { get; set; } = string.Empty;
+    public string Lang { get; set; } = "en";
+}
+```
+
+From SharepointToolbox/Core/Models/TenantProfile.cs:
+```csharp
+namespace SharepointToolbox.Core.Models;
+
+public class TenantProfile
+{
+    public string Name { get; set; } = string.Empty;
+    public string TenantUrl { get; set; } = string.Empty;
+    public string ClientId { get; set; } = string.Empty;
+}
+```
+
+From SharepointToolbox/Infrastructure/Persistence/SettingsRepository.cs:
+```csharp
+namespace SharepointToolbox.Infrastructure.Persistence;
+
+public class SettingsRepository
+{
+    private readonly string _filePath;
+    private readonly SemaphoreSlim _writeLock = new(1, 1);
+
+    public SettingsRepository(string filePath) { _filePath = filePath; }
+    public async Task<AppSettings> LoadAsync() { /* File.ReadAllTextAsync + JsonSerializer.Deserialize */ }
+    public async Task SaveAsync(AppSettings settings) { /* SemaphoreSlim + write-tmp + validate round-trip + File.Move */ }
+}
+```
+
+From SharepointToolbox.Tests/Services/SettingsServiceTests.cs (test pattern):
+```csharp
+[Trait("Category", "Unit")]
+public class SettingsServiceTests : IDisposable
+{
+    private readonly string _tempFile;
+    public SettingsServiceTests() { _tempFile = Path.GetTempFileName(); File.Delete(_tempFile); }
+    public void Dispose() { if (File.Exists(_tempFile)) File.Delete(_tempFile); if (File.Exists(_tempFile + ".tmp")) File.Delete(_tempFile + ".tmp"); }
+    private SettingsRepository CreateRepository() => new(_tempFile);
+}
+```
+</interfaces>
+</context>
+
+<tasks>
+
+<task type="auto" tdd="true">
+  <name>Task 1: Create logo models, BrandingRepository, and repository tests</name>
+  <files>
+    SharepointToolbox/Core/Models/LogoData.cs,
+    SharepointToolbox/Core/Models/BrandingSettings.cs,
+    SharepointToolbox/Core/Models/TenantProfile.cs,
+    SharepointToolbox/Infrastructure/Persistence/BrandingRepository.cs,
+    SharepointToolbox.Tests/Services/BrandingRepositoryTests.cs
+  </files>
+  <behavior>
+    - Test 1: BrandingRepository.LoadAsync returns default BrandingSettings (MspLogo=null) when file does not exist
+    - Test 2: BrandingRepository round-trips BrandingSettings with a non-null MspLogo (Base64 + MimeType preserved)
+    - Test 3: BrandingRepository.SaveAsync creates directory if it does not exist
+    - Test 4: TenantProfile with ClientLogo serializes to JSON with camelCase "clientLogo" key and deserializes back correctly (use System.Text.Json directly)
+    - Test 5: TenantProfile without ClientLogo (null) serializes with clientLogo absent or null and deserializes with ClientLogo=null (forward-compatible)
+  </behavior>
+  <action>
+    1. Create `LogoData.cs` as a non-positional record with `{ get; init; }` properties (NOT positional constructor) to avoid System.Text.Json deserialization pitfall (see RESEARCH Pitfall 3):
+       ```csharp
+       namespace SharepointToolbox.Core.Models;
+       public record LogoData
+       {
+           public string Base64 { get; init; } = string.Empty;
+           public string MimeType { get; init; } = string.Empty;
+       }
+       ```
+
+    2. Create `BrandingSettings.cs`:
+       ```csharp
+       namespace SharepointToolbox.Core.Models;
+       public class BrandingSettings
+       {
+           public LogoData? MspLogo { get; set; }
+       }
+       ```
+
+    3. Extend `TenantProfile.cs` — add ONE property: `public LogoData? ClientLogo { get; set; }`. Do NOT remove or rename any existing properties. This is additive only. ProfileRepository needs no code change — System.Text.Json handles the new nullable property automatically.
+
+    4. Create `BrandingRepository.cs` as an exact structural clone of `SettingsRepository.cs`, substituting `BrandingSettings` for `AppSettings`. Same pattern: `SemaphoreSlim(1,1)`, `File.ReadAllTextAsync`, `JsonSerializer.Deserialize<BrandingSettings>`, write-then-replace with `.tmp` file, `JsonDocument.Parse` validation, `File.Move(overwrite: true)`. Use `PropertyNameCaseInsensitive = true` for Load and `PropertyNamingPolicy = JsonNamingPolicy.CamelCase` + `WriteIndented = true` for Save. Same error handling (InvalidDataException for IO/JSON errors).
+
+    5. Write `BrandingRepositoryTests.cs` following the `SettingsServiceTests` pattern: `IDisposable`, `Path.GetTempFileName()`, cleanup of `.tmp` files, `[Trait("Category", "Unit")]`. Tests for TenantProfile serialization use `JsonSerializer` directly (no repository needed — just confirm the model serializes/deserializes with the new property).
+  </action>
+  <verify>
+    <automated>dotnet test --filter "FullyQualifiedName~BrandingRepositoryTests" --no-build</automated>
+  </verify>
+  <done>LogoData record, BrandingSettings model, TenantProfile.ClientLogo property, and BrandingRepository all exist. Repository round-trips BrandingSettings with MspLogo. TenantProfile with ClientLogo serializes correctly. All tests pass.</done>
+</task>
+
+<task type="auto" tdd="true">
+  <name>Task 2: Create BrandingService with validation, compression, and tests</name>
+  <files>
+    SharepointToolbox/Services/IBrandingService.cs,
+    SharepointToolbox/Services/BrandingService.cs,
+    SharepointToolbox.Tests/Services/BrandingServiceTests.cs
+  </files>
+  <behavior>
+    - Test 1: ImportLogoAsync with valid PNG bytes (magic: 0x89,0x50,0x4E,0x47 + minimal valid content) returns LogoData with MimeType="image/png" and correct Base64
+    - Test 2: ImportLogoAsync with valid JPEG bytes (magic: 0xFF,0xD8,0xFF + minimal content) returns LogoData with MimeType="image/jpeg"
+    - Test 3: ImportLogoAsync with BMP bytes (magic: 0x42,0x4D) throws InvalidDataException with message containing "PNG" and "JPG"
+    - Test 4: ImportLogoAsync with empty file throws InvalidDataException
+    - Test 5: ImportLogoAsync with file under 512 KB returns Base64 matching original bytes exactly (no compression)
+    - Test 6: ImportLogoAsync with file over 512 KB returns LogoData where decoded bytes are <= 512 KB (compressed)
+    - Test 7: SaveMspLogoAsync calls BrandingRepository.SaveAsync with the logo set on BrandingSettings.MspLogo
+    - Test 8: ClearMspLogoAsync saves BrandingSettings with MspLogo=null
+    - Test 9: GetMspLogoAsync returns null when no logo is configured
+  </behavior>
+  <action>
+    1. Create `IBrandingService.cs`:
+       ```csharp
+       namespace SharepointToolbox.Services;
+       public interface IBrandingService
+       {
+           Task<LogoData> ImportLogoAsync(string filePath);
+           Task SaveMspLogoAsync(LogoData logo);
+           Task ClearMspLogoAsync();
+           Task<LogoData?> GetMspLogoAsync();
+       }
+       ```
+       Note: `ImportLogoAsync` is a pure validation+encoding function. It reads the file, validates magic bytes, compresses if needed, and returns `LogoData`. It does NOT persist anything. The caller (ViewModel in Phase 11) decides whether to save as MSP logo or client logo.
+
+    2. Create `BrandingService.cs`:
+       - Constructor takes `BrandingRepository` (same pattern as `SettingsService` taking `SettingsRepository`).
+       - `ImportLogoAsync(string filePath)`:
+         a. Read all bytes via `File.ReadAllBytesAsync`.
+         b. Detect MIME type from magic bytes: PNG signature `0x89,0x50,0x4E,0x47` (first 4 bytes), JPEG signature `0xFF,0xD8,0xFF` (first 3 bytes). If neither matches, throw `InvalidDataException("File format is not PNG or JPG. Only PNG and JPG are accepted.")`.
+         c. If bytes.Length > 512 * 1024, call `CompressToLimit(bytes, mimeType, 512 * 1024)`.
+         d. Return `new LogoData { Base64 = Convert.ToBase64String(bytes), MimeType = mimeType }`.
+       - `CompressToLimit` private static method: Use `System.Drawing.Bitmap` to resize to max 300x300px (proportional scaling) and re-encode at quality 75. Use `System.Drawing.Imaging.ImageCodecInfo.GetImageEncoders()` to find the codec matching the MIME type. Use `EncoderParameters` with `Encoder.Quality` set to 75L. If still over limit after first pass, reduce to 200x200 and quality 50. Return the compressed bytes.
+       - `SaveMspLogoAsync(LogoData logo)`: Load settings from repo, set `MspLogo = logo`, save back.
+       - `ClearMspLogoAsync()`: Load settings, set `MspLogo = null`, save back.
+       - `GetMspLogoAsync()`: Load settings, return `MspLogo` (may be null).
+
+    3. Create `BrandingServiceTests.cs`:
+       - Use `[Trait("Category", "Unit")]` and `IDisposable` pattern.
+       - For magic byte tests: create small byte arrays with correct headers. For PNG, use the 8-byte PNG signature (`0x89,0x50,0x4E,0x47,0x0D,0x0A,0x1A,0x0A`) followed by minimal IHDR+IEND chunks to make a valid 1x1 PNG. For JPEG, use `0xFF,0xD8,0xFF,0xE0` + minimal JFIF header + `0xFF,0xD9` (EOI). Write these to temp files and call `ImportLogoAsync`.
+       - For compression test: generate a valid PNG/JPEG that exceeds 512 KB (e.g., create a 400x400 bitmap filled with random pixels, save as PNG to a temp file, verify it exceeds 512 KB, then call `ImportLogoAsync` and verify result decodes to <= 512 KB).
+       - For SaveMspLogoAsync/ClearMspLogoAsync/GetMspLogoAsync: use real `BrandingRepository` with temp file (same pattern as `SettingsServiceTests`).
+       - Do NOT mock BrandingRepository — the existing test pattern in this codebase uses real file I/O with temp files.
+  </action>
+  <verify>
+    <automated>dotnet test --filter "FullyQualifiedName~BrandingServiceTests" --no-build</automated>
+  </verify>
+  <done>BrandingService validates PNG/JPG via magic bytes, rejects other formats with descriptive error, auto-compresses files over 512 KB, and provides MSP logo CRUD. All tests pass including round-trip through repository.</done>
+</task>
+
+</tasks>
+
+<verification>
+```bash
+dotnet build --no-restore -warnaserror
+dotnet test --filter "FullyQualifiedName~Branding" --no-build
+dotnet test --filter "FullyQualifiedName~ProfileService" --no-build
+```
+All three commands must succeed with zero failures. The ProfileServiceTests confirm TenantProfile changes do not break existing profile persistence.
+</verification>
+
+<success_criteria>
+- LogoData record exists with Base64 and MimeType init properties
+- BrandingSettings class exists with nullable MspLogo property
+- TenantProfile has nullable ClientLogo property (additive, no breaking changes)
+- BrandingRepository persists BrandingSettings to JSON with write-then-replace safety
+- BrandingService validates magic bytes (PNG/JPG only), auto-compresses > 512 KB, and provides MSP logo CRUD
+- All existing tests continue to pass (no regressions from TenantProfile extension)
+- New tests cover: repository round-trip, format validation, compression, rejection, CRUD
+</success_criteria>
+
+<output>
+After completion, create `.planning/phases/10-branding-data-foundation/10-01-SUMMARY.md`
+</output>
@@ -0,0 +1,130 @@
+---
+phase: 10-branding-data-foundation
+plan: 01
+subsystem: branding
+tags: [logo, base64, json-persistence, wpf-imaging, magic-bytes, compression]
+
+requires: []
+
+provides:
+  - LogoData record (Base64 + MimeType init properties) — shared model for all logo storage
+  - BrandingSettings class with nullable MspLogo — MSP-level branding persistence model
+  - TenantProfile.ClientLogo property — per-tenant client logo (additive, no breaking changes)
+  - BrandingRepository — JSON persistence with write-then-replace safety using SemaphoreSlim
+  - IBrandingService / BrandingService — magic byte validation, auto-compression, MSP logo CRUD
+
+affects:
+  - 10-02 (branding UI ViewModel will consume IBrandingService)
+  - 11-report-branding (HTML export will use LogoData from BrandingSettings and TenantProfile)
+  - Phase 13-14 (TenantProfile extended — profile serialization must stay compatible)
+
+tech-stack:
+  added: []
+  patterns:
+    - BrandingRepository mirrors SettingsRepository exactly (SemaphoreSlim write-then-replace, JsonDocument validation)
+    - LogoData as non-positional record with init properties (avoids System.Text.Json positional constructor pitfall)
+    - BrandingService uses WPF PresentationCore (BitmapDecoder/TransformedBitmap/BitmapEncoder) for compression — no new NuGet package required
+    - Magic byte detection (4 bytes PNG, 3 bytes JPEG) before extension check — format is determined by content, not filename
+
+key-files:
+  created:
+    - SharepointToolbox/Core/Models/LogoData.cs
+    - SharepointToolbox/Core/Models/BrandingSettings.cs
+    - SharepointToolbox/Infrastructure/Persistence/BrandingRepository.cs
+    - SharepointToolbox/Services/IBrandingService.cs
+    - SharepointToolbox/Services/BrandingService.cs
+    - SharepointToolbox.Tests/Services/BrandingRepositoryTests.cs
+    - SharepointToolbox.Tests/Services/BrandingServiceTests.cs
+  modified:
+    - SharepointToolbox/Core/Models/TenantProfile.cs
+
+key-decisions:
+  - "Used WPF PresentationCore (BitmapDecoder/TransformedBitmap/JpegBitmapEncoder) for image compression instead of System.Drawing.Bitmap — System.Drawing.Common is not available without a new NuGet package on .NET 10, but WPF PresentationCore is already in the stack (net10.0-windows + UseWPF=true)"
+  - "LogoData is a non-positional record (init properties, not constructor parameters) — prevents System.Text.Json deserialization failure on records with positional constructors"
+  - "BrandingService.ImportLogoAsync is pure (no persistence) — caller decides where to store the LogoData; ViewModel in Phase 11 will call SaveMspLogoAsync or equivalent client logo save"
+
+patterns-established:
+  - "Repository pattern: BrandingRepository is structural clone of SettingsRepository — same SemaphoreSlim(1,1) write lock, write-tmp-then-validate-then-move safety protocol"
+  - "Magic byte validation: PNG checked with 4 bytes (0x89 0x50 0x4E 0x47), JPEG with 3 bytes (0xFF 0xD8 0xFF) — content-based not extension-based"
+  - "Compression two-pass: 300x300 quality 75 first, 200x200 quality 50 if still over limit"
+  - "Test pattern: IDisposable + Path.GetTempFileName() + Dispose cleanup of .tmp files — matches existing SettingsServiceTests"
+
+requirements-completed:
+  - BRAND-01
+  - BRAND-03
+  - BRAND-06
+
+duration: 4min
+completed: 2026-04-08
+---
+
+# Phase 10 Plan 01: Branding Data Foundation Summary
+
+**LogoData record + BrandingRepository (write-then-replace JSON) + BrandingService with PNG/JPEG magic byte validation and WPF-based auto-compression to 512 KB limit**
+
+## Performance
+
+- **Duration:** ~4 min
+- **Started:** 2026-04-08T00:28:31Z
+- **Completed:** 2026-04-08T00:32:26Z
+- **Tasks:** 2
+- **Files modified:** 8 (7 created, 1 modified)
+
+## Accomplishments
+- LogoData record, BrandingSettings model, and TenantProfile.ClientLogo property established as the shared data models for all logo storage across v2.2
+- BrandingRepository persists BrandingSettings to branding.json with write-then-replace safety (SemaphoreSlim + tmp file + JsonDocument validation before move)
+- BrandingService validates PNG/JPEG via magic bytes, rejects all other formats with descriptive error message mentioning PNG and JPG, auto-compresses files over 512 KB using WPF imaging in two passes
+
+## Task Commits
+
+Each task was committed atomically:
+
+1. **Task 1: Create logo models, BrandingRepository, and repository tests** - `2280f12` (feat)
+2. **Task 2: Create BrandingService with validation, compression, and tests** - `1303866` (feat)
+
+## Files Created/Modified
+- `SharepointToolbox/Core/Models/LogoData.cs` - Non-positional record with Base64 and MimeType init properties
+- `SharepointToolbox/Core/Models/BrandingSettings.cs` - MSP logo wrapper with nullable MspLogo property
+- `SharepointToolbox/Core/Models/TenantProfile.cs` - Extended with nullable ClientLogo property (additive only)
+- `SharepointToolbox/Infrastructure/Persistence/BrandingRepository.cs` - JSON persistence mirroring SettingsRepository pattern
+- `SharepointToolbox/Services/IBrandingService.cs` - Interface with ImportLogoAsync, Save/Clear/GetMspLogoAsync
+- `SharepointToolbox/Services/BrandingService.cs` - Magic byte validation, WPF-based compression, MSP logo CRUD
+- `SharepointToolbox.Tests/Services/BrandingRepositoryTests.cs` - 5 tests: defaults, round-trip, dir creation, TenantProfile serialization
+- `SharepointToolbox.Tests/Services/BrandingServiceTests.cs` - 9 tests: PNG/JPEG acceptance, BMP rejection, empty file, no-compression, compression, CRUD
+
+## Decisions Made
+- Used WPF PresentationCore imaging (BitmapDecoder, TransformedBitmap, JpegBitmapEncoder) for compression — `System.Drawing.Common` is not available without a new NuGet package on .NET 10 and is not in the existing stack
+- `ImportLogoAsync` is kept pure (no persistence side-effects) — caller decides where to store the returned `LogoData`, enabling reuse for both MSP logo and per-tenant client logo paths
+
+## Deviations from Plan
+
+### Auto-fixed Issues
+
+**1. [Rule 1 - Bug] Used WPF PresentationCore instead of System.Drawing.Bitmap for compression**
+- **Found during:** Task 2 (BrandingService implementation)
+- **Issue:** Plan specified `System.Drawing.Bitmap` and `ImageCodecInfo`, but `System.Drawing.Common` is not in the project's package list and is not available on .NET 10 without an explicit NuGet package reference. Adding it would violate the v2.2 constraint ("No new NuGet packages")
+- **Fix:** Implemented compression using `System.Windows.Media.Imaging` classes (BitmapDecoder, TransformedBitmap, JpegBitmapEncoder, PngBitmapEncoder) — fully available via WPF PresentationCore which is already in the stack
+- **Files modified:** SharepointToolbox/Services/BrandingService.cs
+- **Verification:** All 9 BrandingServiceTests pass including the compression test (400x400 random-pixel PNG over 512 KB compressed to under 512 KB)
+- **Committed in:** 1303866 (Task 2 commit)
+
+---
+
+**Total deviations:** 1 auto-fixed (Rule 1 — implementation approach)
+**Impact on plan:** No scope change. Compression behavior is identical: proportional resize to 300x300 at quality 75, then 200x200 at quality 50 if still over limit. WPF APIs provide the same capability without a new dependency.
+
+## Issues Encountered
+None — build and all tests passed first time after implementation.
+
+## User Setup Required
+None - no external service configuration required.
+
+## Next Phase Readiness
+- All logo storage models and infrastructure are ready for Phase 10 Plan 02 (branding UI ViewModel)
+- BrandingService.ImportLogoAsync is the entry point for logo import flows in Phase 11
+- TenantProfile.ClientLogo is ready; ProfileRepository requires no code changes (System.Text.Json handles the new nullable property automatically)
+- 14 total Branding tests passing; 10 ProfileService tests confirm no regression from TenantProfile extension
+
+---
+*Phase: 10-branding-data-foundation*
+*Completed: 2026-04-08*
@@ -0,0 +1,235 @@
+---
+phase: 10-branding-data-foundation
+plan: 02
+type: execute
+wave: 1
+depends_on: []
+files_modified:
+  - SharepointToolbox/Core/Models/GraphDirectoryUser.cs
+  - SharepointToolbox/Services/IGraphUserDirectoryService.cs
+  - SharepointToolbox/Services/GraphUserDirectoryService.cs
+  - SharepointToolbox.Tests/Services/GraphUserDirectoryServiceTests.cs
+autonomous: true
+requirements:
+  - BRAND-06
+
+must_haves:
+  truths:
+    - "GetUsersAsync returns all enabled member users following @odata.nextLink until exhausted"
+    - "GetUsersAsync respects CancellationToken and stops iteration when cancelled"
+    - "Each returned user includes DisplayName, UserPrincipalName, Mail, Department, and JobTitle"
+  artifacts:
+    - path: "SharepointToolbox/Core/Models/GraphDirectoryUser.cs"
+      provides: "Result record for directory enumeration"
+      contains: "record GraphDirectoryUser"
+    - path: "SharepointToolbox/Services/IGraphUserDirectoryService.cs"
+      provides: "Interface for directory enumeration"
+      exports: ["GetUsersAsync"]
+    - path: "SharepointToolbox/Services/GraphUserDirectoryService.cs"
+      provides: "PageIterator-based Graph user enumeration"
+      contains: "PageIterator"
+    - path: "SharepointToolbox.Tests/Services/GraphUserDirectoryServiceTests.cs"
+      provides: "Unit tests for directory service"
+      min_lines: 40
+  key_links:
+    - from: "SharepointToolbox/Services/GraphUserDirectoryService.cs"
+      to: "SharepointToolbox/Infrastructure/Auth/GraphClientFactory.cs"
+      via: "constructor injection"
+      pattern: "GraphClientFactory"
+    - from: "SharepointToolbox/Services/GraphUserDirectoryService.cs"
+      to: "Microsoft.Graph PageIterator"
+      via: "SDK pagination"
+      pattern: "PageIterator<User, UserCollectionResponse>"
+---
+
+<objective>
+Create the Graph user directory service for paginated tenant user enumeration.
+
+Purpose: Phase 13 (User Directory ViewModel) needs a service that enumerates all enabled member users from a tenant via Microsoft Graph with pagination. This plan builds the infrastructure service and its tests.
+
+Output: GraphDirectoryUser model, IGraphUserDirectoryService interface, GraphUserDirectoryService implementation with PageIterator, and unit tests.
+</objective>
+
+<execution_context>
+@C:/Users/dev/.claude/get-shit-done/workflows/execute-plan.md
+@C:/Users/dev/.claude/get-shit-done/templates/summary.md
+</execution_context>
+
+<context>
+@.planning/PROJECT.md
+@.planning/ROADMAP.md
+@.planning/STATE.md
+@.planning/phases/10-branding-data-foundation/10-RESEARCH.md
+
+<interfaces>
+<!-- Existing Graph service pattern to follow. -->
+
+From SharepointToolbox/Services/IGraphUserSearchService.cs:
+```csharp
+namespace SharepointToolbox.Services;
+
+public interface IGraphUserSearchService
+{
+    Task<IReadOnlyList<GraphUserResult>> SearchUsersAsync(
+        string clientId,
+        string query,
+        int maxResults = 10,
+        CancellationToken ct = default);
+}
+
+public record GraphUserResult(string DisplayName, string UserPrincipalName, string? Mail);
+```
+
+From SharepointToolbox/Services/GraphUserSearchService.cs:
+```csharp
+public class GraphUserSearchService : IGraphUserSearchService
+{
+    private readonly GraphClientFactory _graphClientFactory;
+
+    public GraphUserSearchService(GraphClientFactory graphClientFactory)
+    {
+        _graphClientFactory = graphClientFactory;
+    }
+
+    public async Task<IReadOnlyList<GraphUserResult>> SearchUsersAsync(
+        string clientId, string query, int maxResults = 10, CancellationToken ct = default)
+    {
+        var graphClient = await _graphClientFactory.CreateClientAsync(clientId, ct);
+        var response = await graphClient.Users.GetAsync(config =>
+        {
+            config.QueryParameters.Filter = $"startsWith(displayName,'{escapedQuery}')...";
+            config.QueryParameters.Select = new[] { "displayName", "userPrincipalName", "mail" };
+            config.QueryParameters.Top = maxResults;
+            config.Headers.Add("ConsistencyLevel", "eventual");
+            config.QueryParameters.Count = true;
+        }, ct);
+        // ...map response.Value to GraphUserResult list
+    }
+}
+```
+
+From SharepointToolbox/Infrastructure/Auth/GraphClientFactory.cs:
+```csharp
+public class GraphClientFactory
+{
+    private readonly MsalClientFactory _msalFactory;
+    public GraphClientFactory(MsalClientFactory msalFactory) { _msalFactory = msalFactory; }
+    public async Task<GraphServiceClient> CreateClientAsync(string clientId, CancellationToken ct) { /* ... */ }
+}
+```
+</interfaces>
+</context>
+
+<tasks>
+
+<task type="auto" tdd="true">
+  <name>Task 1: Create GraphDirectoryUser model and IGraphUserDirectoryService interface</name>
+  <files>
+    SharepointToolbox/Core/Models/GraphDirectoryUser.cs,
+    SharepointToolbox/Services/IGraphUserDirectoryService.cs
+  </files>
+  <behavior>
+    - GraphDirectoryUser is a positional record with DisplayName (string), UserPrincipalName (string), Mail (string?), Department (string?), JobTitle (string?)
+    - IGraphUserDirectoryService declares GetUsersAsync(string clientId, IProgress&lt;int&gt;? progress, CancellationToken ct) returning Task&lt;IReadOnlyList&lt;GraphDirectoryUser&gt;&gt;
+  </behavior>
+  <action>
+    1. Create `GraphDirectoryUser.cs` in `Core/Models/`:
+       ```csharp
+       namespace SharepointToolbox.Core.Models;
+       public record GraphDirectoryUser(
+           string DisplayName,
+           string UserPrincipalName,
+           string? Mail,
+           string? Department,
+           string? JobTitle);
+       ```
+       This is a positional record (fine here since it's never JSON-deserialized — it's only constructed in code from Graph SDK User objects).
+
+    2. Create `IGraphUserDirectoryService.cs` in `Services/`:
+       ```csharp
+       namespace SharepointToolbox.Services;
+       public interface IGraphUserDirectoryService
+       {
+           Task<IReadOnlyList<GraphDirectoryUser>> GetUsersAsync(
+               string clientId,
+               IProgress<int>? progress = null,
+               CancellationToken ct = default);
+       }
+       ```
+       The `IProgress<int>` parameter reports the running count of users fetched so far — Phase 13's ViewModel will use this to show "Loading... X users" feedback. It's optional (null = no reporting).
+  </action>
+  <verify>
+    <automated>dotnet build --no-restore -warnaserror</automated>
+  </verify>
+  <done>GraphDirectoryUser record and IGraphUserDirectoryService interface exist and compile without warnings.</done>
+</task>
+
+<task type="auto" tdd="true">
+  <name>Task 2: Implement GraphUserDirectoryService with PageIterator and tests</name>
+  <files>
+    SharepointToolbox/Services/GraphUserDirectoryService.cs,
+    SharepointToolbox.Tests/Services/GraphUserDirectoryServiceTests.cs
+  </files>
+  <behavior>
+    - Test 1: GetUsersAsync with mocked GraphClientFactory returns mapped GraphDirectoryUser records with all 5 fields
+    - Test 2: GetUsersAsync reports progress via IProgress&lt;int&gt; with incrementing user count
+    - Test 3: GetUsersAsync with cancelled token throws OperationCanceledException or returns partial results
+  </behavior>
+  <action>
+    1. Create `GraphUserDirectoryService.cs`:
+       - Constructor takes `GraphClientFactory` (same pattern as `GraphUserSearchService`).
+       - `GetUsersAsync` implementation:
+         a. Get `GraphServiceClient` via `_graphClientFactory.CreateClientAsync(clientId, ct)`.
+         b. Call `graphClient.Users.GetAsync(config => { ... }, ct)` with:
+            - `config.QueryParameters.Filter = "accountEnabled eq true and userType eq 'Member'"` — standard equality filter, does NOT require ConsistencyLevel: eventual (unlike GraphUserSearchService which uses startsWith). Do NOT add ConsistencyLevel header. Do NOT add $count.
+            - `config.QueryParameters.Select = new[] { "displayName", "userPrincipalName", "mail", "department", "jobTitle" }`
+            - `config.QueryParameters.Top = 999`
+         c. If response is null, return empty list.
+         d. Create `PageIterator<User, UserCollectionResponse>.CreatePageIterator(graphClient, response, callback)`.
+         e. In the callback:
+            - Check `ct.IsCancellationRequested` — if true, `return false` to stop iteration (see RESEARCH Pitfall 2).
+            - Map User to GraphDirectoryUser: `new GraphDirectoryUser(user.DisplayName ?? user.UserPrincipalName ?? string.Empty, user.UserPrincipalName ?? string.Empty, user.Mail, user.Department, user.JobTitle)`.
+            - Add to results list.
+            - Report progress: `progress?.Report(results.Count)`.
+            - Return true to continue.
+         f. Call `await pageIterator.IterateAsync(ct)`.
+         g. Return results as `IReadOnlyList<GraphDirectoryUser>`.
+       - Add a comment on the filter line: `// Pending real-tenant verification — see STATE.md pending todos`
+
+    2. Create `GraphUserDirectoryServiceTests.cs`:
+       - Use `[Trait("Category", "Unit")]`.
+       - Testing PageIterator with mocks is complex because `PageIterator` requires a real `GraphServiceClient`. Instead, test at a higher level:
+         a. Create a mock `GraphClientFactory` using Moq that returns a mock `GraphServiceClient`.
+         b. For the basic mapping test: mock `graphClient.Users.GetAsync()` to return a `UserCollectionResponse` with a list of test `User` objects (no `@odata.nextLink` = single page). Verify the returned `GraphDirectoryUser` list has correct field mapping.
+         c. For the progress test: same setup, verify `IProgress<int>.Report` is called with incrementing counts.
+         d. For cancellation: use a pre-cancelled `CancellationTokenSource`. The `GetAsync` call should throw `OperationCanceledException` or the callback should detect cancellation.
+       - If mocking `GraphServiceClient.Users.GetAsync` proves too complex with the Graph SDK's request builder pattern, mark the test with `[Fact(Skip = "Requires integration test with real Graph client")]` and add a comment explaining why. The critical thing is the test FILE exists with the intent documented.
+       - Focus on what IS testable without a real Graph endpoint: the mapping logic. Consider extracting a static `MapUser(User user)` method and testing that directly.
+  </action>
+  <verify>
+    <automated>dotnet test --filter "FullyQualifiedName~GraphUserDirectoryServiceTests" --no-build</automated>
+  </verify>
+  <done>GraphUserDirectoryService exists with PageIterator pagination, cancellation support via callback check, progress reporting, and correct filter (no ConsistencyLevel). Tests verify mapping logic and exist for pagination/cancellation scenarios.</done>
+</task>
+
+</tasks>
+
+<verification>
+```bash
+dotnet build --no-restore -warnaserror
+dotnet test --filter "FullyQualifiedName~GraphUserDirectoryService" --no-build
+```
+Both commands must succeed. No warnings, no test failures.
+</verification>
+
+<success_criteria>
+- GraphDirectoryUser record has all 5 fields (DisplayName, UPN, Mail, Department, JobTitle)
+- IGraphUserDirectoryService interface declares GetUsersAsync with clientId, progress, and cancellation
+- GraphUserDirectoryService uses PageIterator for pagination, checks cancellation in callback, reports progress
+- Filter is "accountEnabled eq true and userType eq 'Member'" WITHOUT ConsistencyLevel header
+- Tests exist and pass for mapping logic; pagination/cancellation tests are either passing or skipped with clear justification
+</success_criteria>
+
+<output>
+After completion, create `.planning/phases/10-branding-data-foundation/10-02-SUMMARY.md`
+</output>
@@ -0,0 +1,130 @@
+---
+phase: 10-branding-data-foundation
+plan: "02"
+subsystem: api
+tags: [microsoft-graph, graph-sdk, pagination, page-iterator, csharp, directory-service]
+
+# Dependency graph
+requires:
+  - phase: 10-branding-data-foundation-01
+    provides: "GraphClientFactory (existing) and project infrastructure"
+provides:
+  - "GraphDirectoryUser record (DisplayName, UPN, Mail, Department, JobTitle)"
+  - "IGraphUserDirectoryService interface with GetUsersAsync(clientId, progress, ct)"
+  - "GraphUserDirectoryService implementation with PageIterator-based pagination"
+  - "MapUser static method testable without live Graph endpoint"
+  - "GraphUserDirectoryServiceTests with 5 unit tests for mapping logic"
+affects:
+  - phase-13-user-directory-viewmodel
+  - phase-14-user-directory-ui
+
+# Tech tracking
+tech-stack:
+  added: []
+  patterns:
+    - "PageIterator<User, UserCollectionResponse> for multi-page Graph enumeration"
+    - "Cancellation-in-callback pattern: callback returns false when ct.IsCancellationRequested"
+    - "IProgress<int> reporting running count for ViewModel loading feedback"
+    - "AppGraphClientFactory alias to disambiguate SharepointToolbox.Infrastructure.Auth.GraphClientFactory from Microsoft.Graph.GraphClientFactory"
+    - "Extract MapUser as internal static for direct unit testability without live Graph"
+
+key-files:
+  created:
+    - SharepointToolbox/Core/Models/GraphDirectoryUser.cs
+    - SharepointToolbox/Services/IGraphUserDirectoryService.cs
+    - SharepointToolbox/Services/GraphUserDirectoryService.cs
+    - SharepointToolbox.Tests/Services/GraphUserDirectoryServiceTests.cs
+  modified: []
+
+key-decisions:
+  - "No ConsistencyLevel: eventual header on the directory filter (accountEnabled eq true and userType eq 'Member') — standard equality filter does not require it, unlike startsWith queries in GraphUserSearchService"
+  - "MapUser extracted as internal static method to decouple mapping logic from PageIterator, enabling direct unit tests without a live Graph client"
+  - "Integration tests for pagination/cancellation skipped with documented rationale — PageIterator uses internal GraphServiceClient internals not mockable via Moq"
+  - "Type alias AppGraphClientFactory used to resolve ambiguity with Microsoft.Graph.GraphClientFactory in the same namespace"
+
+patterns-established:
+  - "IProgress<int> optional progress pattern: pass null for no reporting, non-null for ViewModel loading UX"
+  - "PageIterator cancellation: check ct.IsCancellationRequested inside callback, return false to stop"
+
+requirements-completed:
+  - BRAND-06
+
+# Metrics
+duration: 4min
+completed: 2026-04-08
+---
+
+# Phase 10 Plan 02: Graph User Directory Service Summary
+
+**Graph SDK PageIterator service for full-tenant member enumeration with cancellation, progress reporting, and 5-field user mapping**
+
+## Performance
+
+- **Duration:** 4 min
+- **Started:** 2026-04-08T10:28:36Z
+- **Completed:** 2026-04-08T10:32:20Z
+- **Tasks:** 2
+- **Files modified:** 4 created
+
+## Accomplishments
+
+- GraphDirectoryUser record with all 5 required fields (DisplayName, UPN, Mail, Department, JobTitle)
+- IGraphUserDirectoryService interface with IProgress<int> optional parameter for loading feedback
+- GraphUserDirectoryService using PageIterator for transparent multi-page Graph enumeration with callback-based cancellation
+- 5 unit tests covering all MapUser field-mapping scenarios including null fallback chains
+
+## Task Commits
+
+Each task was committed atomically:
+
+1. **Task 1: Create GraphDirectoryUser model and IGraphUserDirectoryService interface** - `5e56a96` (feat)
+2. **Task 2: Implement GraphUserDirectoryService with PageIterator and tests** - `3ba5746` (feat)
+
+## Files Created/Modified
+
+- `SharepointToolbox/Core/Models/GraphDirectoryUser.cs` - Positional record with 5 fields for directory enumeration results
+- `SharepointToolbox/Services/IGraphUserDirectoryService.cs` - Interface with GetUsersAsync(clientId, IProgress<int>?, CancellationToken)
+- `SharepointToolbox/Services/GraphUserDirectoryService.cs` - PageIterator implementation, cancellation in callback, progress reporting, no ConsistencyLevel header
+- `SharepointToolbox.Tests/Services/GraphUserDirectoryServiceTests.cs` - 5 MapUser unit tests + 4 integration tests skipped with documented rationale
+
+## Decisions Made
+
+- No ConsistencyLevel header on the equality filter (different from GraphUserSearchService which uses startsWith and requires eventual consistency)
+- MapUser extracted as internal static to allow direct unit testing of mapping logic without requiring PageIterator and a live Graph client
+- Integration-level tests for pagination/cancellation documented as skipped: PageIterator's internal request execution is not mockable via Moq without a real GraphServiceClient
+
+## Deviations from Plan
+
+### Auto-fixed Issues
+
+**1. [Rule 1 - Bug] Resolved ambiguous GraphClientFactory reference**
+- **Found during:** Task 2 (GraphUserDirectoryService implementation)
+- **Issue:** `using Microsoft.Graph;` combined with `using SharepointToolbox.Infrastructure.Auth;` created an ambiguous reference — both namespaces define `GraphClientFactory`. Build error CS0104.
+- **Fix:** Added type alias `using AppGraphClientFactory = SharepointToolbox.Infrastructure.Auth.GraphClientFactory;` and removed the generic using for the auth namespace.
+- **Files modified:** `SharepointToolbox/Services/GraphUserDirectoryService.cs`
+- **Verification:** `dotnet build SharepointToolbox/SharepointToolbox.csproj --no-restore -warnaserror` succeeds with 0 warnings, 0 errors.
+- **Committed in:** `3ba5746` (Task 2 commit)
+
+---
+
+**Total deviations:** 1 auto-fixed (Rule 1 - Bug)
+**Impact on plan:** Fix necessary for compilation. No scope creep.
+
+## Issues Encountered
+
+- Pre-existing `BrandingServiceTests.cs` (untracked) references `BrandingService` types not yet created (awaiting full plan 10-01 execution). This prevented `dotnet test` from running after rebuilding the test project. Tests were verified to compile via direct inspection; main project builds with zero warnings. Logged in `deferred-items.md`. Will be resolved when plan 10-01 is fully executed.
+
+## User Setup Required
+
+None - no external service configuration required.
+
+## Next Phase Readiness
+
+- GraphUserDirectoryService is ready for injection into Phase 13's User Directory ViewModel
+- IProgress<int> parameter provides the running count hook Phase 13 needs for "Loading... X users" UX
+- Pending real-tenant verification of the filter (noted in STATE.md and code comment)
+- BrandingService (plan 10-01 remainder) must be completed to restore test project compilation
+
+---
+*Phase: 10-branding-data-foundation*
+*Completed: 2026-04-08*
@@ -0,0 +1,145 @@
+---
+phase: 10-branding-data-foundation
+plan: 03
+type: execute
+wave: 2
+depends_on:
+  - 10-01
+  - 10-02
+files_modified:
+  - SharepointToolbox/App.xaml.cs
+autonomous: true
+requirements:
+  - BRAND-01
+  - BRAND-03
+  - BRAND-06
+
+must_haves:
+  truths:
+    - "BrandingRepository, BrandingService, and GraphUserDirectoryService are resolved by DI without runtime errors"
+    - "The full test suite passes including all new and existing tests"
+  artifacts:
+    - path: "SharepointToolbox/App.xaml.cs"
+      provides: "DI registration for Phase 10 services"
+      contains: "BrandingRepository"
+  key_links:
+    - from: "SharepointToolbox/App.xaml.cs"
+      to: "SharepointToolbox/Infrastructure/Persistence/BrandingRepository.cs"
+      via: "AddSingleton registration"
+      pattern: "BrandingRepository.*branding\\.json"
+    - from: "SharepointToolbox/App.xaml.cs"
+      to: "SharepointToolbox/Services/BrandingService.cs"
+      via: "AddSingleton registration"
+      pattern: "AddSingleton<BrandingService>"
+    - from: "SharepointToolbox/App.xaml.cs"
+      to: "SharepointToolbox/Services/GraphUserDirectoryService.cs"
+      via: "AddTransient registration"
+      pattern: "IGraphUserDirectoryService.*GraphUserDirectoryService"
+---
+
+<objective>
+Register all Phase 10 services in the DI container and run the full test suite to confirm no regressions.
+
+Purpose: Without DI registration, none of the new services are available at runtime. This plan wires BrandingRepository, BrandingService, and GraphUserDirectoryService into App.xaml.cs following established patterns.
+
+Output: Updated App.xaml.cs with Phase 10 DI registrations. Full test suite green.
+</objective>
+
+<execution_context>
+@C:/Users/dev/.claude/get-shit-done/workflows/execute-plan.md
+@C:/Users/dev/.claude/get-shit-done/templates/summary.md
+</execution_context>
+
+<context>
+@.planning/PROJECT.md
+@.planning/ROADMAP.md
+@.planning/STATE.md
+@.planning/phases/10-branding-data-foundation/10-01-SUMMARY.md
+@.planning/phases/10-branding-data-foundation/10-02-SUMMARY.md
+
+<interfaces>
+<!-- DI registration pattern from App.xaml.cs (lines 73-163). -->
+
+From SharepointToolbox/App.xaml.cs:
+```csharp
+private static void RegisterServices(HostBuilderContext ctx, IServiceCollection services)
+{
+    var appData = Path.Combine(
+        Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData),
+        "SharepointToolbox");
+    services.AddSingleton(_ => new ProfileRepository(Path.Combine(appData, "profiles.json")));
+    services.AddSingleton(_ => new SettingsRepository(Path.Combine(appData, "settings.json")));
+    services.AddSingleton<MsalClientFactory>();
+    services.AddSingleton<SessionManager>();
+    // ... more registrations ...
+    services.AddSingleton<GraphClientFactory>();
+    // ... more registrations ...
+}
+```
+
+From 10-RESEARCH.md Pattern 7:
+```csharp
+// Phase 10: Branding Data Foundation
+services.AddSingleton(_ => new BrandingRepository(Path.Combine(appData, "branding.json")));
+services.AddSingleton<IBrandingService, BrandingService>();
+services.AddTransient<IGraphUserDirectoryService, GraphUserDirectoryService>();
+```
+</interfaces>
+</context>
+
+<tasks>
+
+<task type="auto">
+  <name>Task 1: Register Phase 10 services in DI and run full test suite</name>
+  <files>SharepointToolbox/App.xaml.cs</files>
+  <action>
+    1. Open `SharepointToolbox/App.xaml.cs` and locate the `RegisterServices` method.
+
+    2. Add a new section comment and three registrations AFTER the existing `SettingsRepository` registration (around line 79) and BEFORE the `MsalClientFactory` line. Place them logically with the other repository/service registrations:
+       ```csharp
+       // Phase 10: Branding Data Foundation
+       services.AddSingleton(_ => new BrandingRepository(Path.Combine(appData, "branding.json")));
+       services.AddSingleton<IBrandingService, BrandingService>();
+       services.AddTransient<IGraphUserDirectoryService, GraphUserDirectoryService>();
+       ```
+
+    3. Add the necessary `using` statements at the top of the file if not already present:
+       - `using SharepointToolbox.Infrastructure.Persistence;` (likely already present for ProfileRepository/SettingsRepository)
+       - `using SharepointToolbox.Services;` (likely already present for other service registrations)
+
+    4. Rationale for lifetimes per RESEARCH:
+       - `BrandingRepository`: Singleton — single file, shared SemaphoreSlim lock (same as ProfileRepository and SettingsRepository).
+       - `BrandingService` (as `IBrandingService`): Singleton — stateless after construction, depends on singleton repository.
+       - `GraphUserDirectoryService` (as `IGraphUserDirectoryService`): Transient — stateless, per-call usage, different tenants.
+
+    5. Build and run the full test suite to confirm zero regressions:
+       ```bash
+       dotnet build --no-restore -warnaserror
+       dotnet test
+       ```
+  </action>
+  <verify>
+    <automated>dotnet build --no-restore -warnaserror && dotnet test</automated>
+  </verify>
+  <done>App.xaml.cs has Phase 10 DI registrations. Full build succeeds with zero warnings. Full test suite passes with zero failures.</done>
+</task>
+
+</tasks>
+
+<verification>
+```bash
+dotnet build --no-restore -warnaserror
+dotnet test
+```
+Both must succeed. Zero warnings, zero test failures. This is the phase gate.
+</verification>
+
+<success_criteria>
+- App.xaml.cs registers BrandingRepository (Singleton, branding.json), IBrandingService/BrandingService (Singleton), IGraphUserDirectoryService/GraphUserDirectoryService (Transient)
+- Full build passes with -warnaserror
+- Full test suite passes (all existing + all new tests)
+</success_criteria>
+
+<output>
+After completion, create `.planning/phases/10-branding-data-foundation/10-03-SUMMARY.md`
+</output>
@@ -0,0 +1,114 @@
+---
+phase: 10-branding-data-foundation
+plan: "03"
+subsystem: infra
+tags: [di, dependency-injection, ioc-container, branding, graph-directory, wpf]
+
+# Dependency graph
+requires:
+  - phase: 10-branding-data-foundation-01
+    provides: "BrandingRepository, IBrandingService/BrandingService"
+  - phase: 10-branding-data-foundation-02
+    provides: "IGraphUserDirectoryService/GraphUserDirectoryService"
+
+provides:
+  - "BrandingRepository registered as Singleton in DI (branding.json path)"
+  - "IBrandingService/BrandingService registered as Singleton in DI"
+  - "IGraphUserDirectoryService/GraphUserDirectoryService registered as Transient in DI"
+  - "Phase 10 services fully wired — resolvable at runtime"
+
+affects:
+  - phase-11-report-branding
+  - phase-13-user-directory-viewmodel
+  - phase-14-user-directory-ui
+
+# Tech tracking
+tech-stack:
+  added: []
+  patterns:
+    - "Phase 10 DI block placed after SettingsRepository, before MsalClientFactory — grouped with other repository/infrastructure singletons"
+    - "BrandingRepository: Singleton lifetime matching ProfileRepository/SettingsRepository (single file, shared SemaphoreSlim)"
+    - "IBrandingService: Singleton lifetime — stateless after construction, depends on singleton BrandingRepository"
+    - "IGraphUserDirectoryService: Transient lifetime — stateless, per-call, designed for multiple-tenant scenarios"
+
+key-files:
+  created: []
+  modified:
+    - SharepointToolbox/App.xaml.cs
+
+key-decisions:
+  - "No new using statements required — SharepointToolbox.Infrastructure.Persistence and SharepointToolbox.Services were already imported from prior phases"
+
+patterns-established:
+  - "Phase section comment pattern: each new phase block labeled with '// Phase N: Name' comment for orientation in RegisterServices"
+
+requirements-completed:
+  - BRAND-01
+  - BRAND-03
+  - BRAND-06
+
+# Metrics
+duration: 5min
+completed: 2026-04-08
+---
+
+# Phase 10 Plan 03: DI Registration Summary
+
+**BrandingRepository (Singleton), IBrandingService (Singleton), and IGraphUserDirectoryService (Transient) wired into App.xaml.cs — 224 tests pass, zero regressions**
+
+## Performance
+
+- **Duration:** ~5 min
+- **Started:** 2026-04-08T10:34:43Z
+- **Completed:** 2026-04-08T10:39:00Z
+- **Tasks:** 1
+- **Files modified:** 1
+
+## Accomplishments
+
+- All three Phase 10 services registered in the application's DI container with correct lifetimes
+- Main project builds with zero warnings under `-warnaserror`
+- Full test suite: 224 passed, 26 skipped (integration tests requiring live Graph), 0 failed
+
+## Task Commits
+
+Each task was committed atomically:
+
+1. **Task 1: Register Phase 10 services in DI and run full test suite** - `7e8e228` (feat)
+
+## Files Created/Modified
+
+- `SharepointToolbox/App.xaml.cs` - Added Phase 10 DI block: BrandingRepository (Singleton, branding.json), IBrandingService/BrandingService (Singleton), IGraphUserDirectoryService/GraphUserDirectoryService (Transient)
+
+## Decisions Made
+
+None - followed plan as specified. The `using` directives for `SharepointToolbox.Infrastructure.Persistence` and `SharepointToolbox.Services` were already present, so no additional imports were needed.
+
+## Deviations from Plan
+
+None - plan executed exactly as written.
+
+## Issues Encountered
+
+One flaky test failure (`CanExport_true_when_has_results`) occurred during the first full suite run. This test uses `WeakReferenceMessenger` with async ViewModel operations and is timing-sensitive. Re-running the specific test and then the full suite both passed. The failure was not caused by my DI changes (the test uses direct constructor injection with mocks — no DI container involved). The test passed on all subsequent runs.
+
+## User Setup Required
+
+None - no external service configuration required.
+
+## Next Phase Readiness
+
+- All Phase 10 services resolve at runtime without errors
+- Phase 11 (report branding) can inject `IBrandingService` into export services and ViewModels
+- Phase 13 (user directory ViewModel) can inject `IGraphUserDirectoryService`
+- BrandingRepository will create `branding.json` on first write, in the existing AppData directory — no manual setup needed
+
+---
+*Phase: 10-branding-data-foundation*
+*Completed: 2026-04-08*
+
+## Self-Check: PASSED
+
+- FOUND: SharepointToolbox/App.xaml.cs (with Phase 10 registrations)
+- FOUND: .planning/phases/10-branding-data-foundation/10-03-SUMMARY.md
+- FOUND commit: 7e8e228 (feat(10-03): register Phase 10 services in DI container)
@@ -0,0 +1,79 @@
+---
+phase: 10
+title: Branding Data Foundation
+status: ready-for-planning
+created: 2026-04-08
+---
+
+# Phase 10 Context: Branding Data Foundation
+
+## Decided Areas (from prior research + STATE.md)
+
+These are locked — do not re-litigate during planning or execution.
+
+| Decision | Value |
+|---|---|
+| Logo storage format | Base64 strings in JSON (not file paths) |
+| MSP logo location | `BrandingSettings.cs` model → `branding.json` |
+| Client logo location | On `TenantProfile` model (per-tenant) |
+| File path after import | Discarded — only base64 persists |
+| SVG support | Rejected (XSS risk) — PNG/JPG only |
+| User directory service | New `GraphUserDirectoryService`, separate from `GraphUserSearchService` |
+| Directory auto-load | No — explicit "Load Directory" button required |
+| New NuGet packages | None — existing stack covers everything |
+| Export service signature | Optional `ReportBranding? branding = null` parameter on existing export methods |
+
+## Discussed Areas
+
+### 1. Logo Metadata Model
+
+**Decision:** Store base64 + MIME type as separate fields in a shared `LogoData` record.
+
+- Shared model: `LogoData { string Base64, string MimeType }` — used by both MSP logo (in `BrandingSettings`) and client logo (on `TenantProfile`)
+- `MimeType` is `"image/png"` or `"image/jpeg"`, determined at import time from magic bytes
+- No other metadata stored — no original filename, dimensions, or import date
+- Export services concatenate `data:{MimeType};base64,{Base64}` for HTML `<img>` tags
+- WPF preview converts `Base64` bytes to `BitmapImage` directly
+
+### 2. Logo Validation & Compression
+
+**Decision:** Validate format via magic bytes, auto-compress oversized files silently.
+
+- **Format detection:** Read file header magic bytes only — ignore file extension entirely
+  - PNG signature: `89 50 4E 47` (first 4 bytes)
+  - JPEG signature: `FF D8 FF` (first 3 bytes)
+  - Anything else → reject with specific error message (e.g., "File format is BMP, only PNG and JPG are accepted")
+- **Size handling:** If file exceeds 512 KB, auto-compress silently (no user notification)
+  - Strategy: resize dimensions (e.g., max 300px width/height) + reduce quality
+  - Keep original format — PNG stays PNG, JPEG stays JPEG (no format conversion)
+  - Compress until under 512 KB
+- **Dimension limits:** None — the 512 KB cap and compression handle naturally
+- **Validation errors:** Specific messages for format rejection (format-related only, since size is auto-handled)
+
+### 3. Profile Deletion & Duplication Behavior
+
+**Decision:** Warn about logo loss on deletion; do NOT copy logo on duplication.
+
+- **Deletion:** When deleting a tenant profile that has a client logo, the confirmation message explicitly mentions it: "This will also remove its client logo." The logo is embedded in the profile JSON, so deletion is automatic — no orphaned files.
+- **Duplication:** Duplicating a tenant profile copies connection fields (Name, TenantUrl, ClientId) but starts with a blank client logo. The user must re-import or auto-pull for the new profile. Rationale: duplicated profiles are typically for different tenants, so the logo shouldn't carry over.
+
+## Deferred Ideas (out of scope for Phase 10)
+
+- Logo preview in Settings UI (Phase 12)
+- Auto-pull client logo from Entra branding API (Phase 11/12)
+- Report header layout with logos side-by-side (Phase 11)
+- "Load Directory" button placement decision (Phase 14)
+- Session-scoped directory cache (UDIR-F01, deferred)
+
+## code_context
+
+| Asset | Path | Reuse |
+|---|---|---|
+| TenantProfile model | `SharepointToolbox/Core/Models/TenantProfile.cs` | Extend with `LogoData? ClientLogo` property |
+| AppSettings model | `SharepointToolbox/Core/Models/AppSettings.cs` | Reference for BrandingSettings pattern |
+| SettingsRepository | `SharepointToolbox/Infrastructure/Persistence/SettingsRepository.cs` | Clone pattern for BrandingRepository (write-then-replace + SemaphoreSlim) |
+| ProfileRepository | `SharepointToolbox/Infrastructure/Persistence/ProfileRepository.cs` | Already handles TenantProfile persistence — will serialize new logo field |
+| GraphUserSearchService | `SharepointToolbox/Services/GraphUserSearchService.cs` | Reference for Graph SDK usage, auth, and query patterns |
+| GraphClientFactory | `SharepointToolbox/Infrastructure/Auth/GraphClientFactory.cs` | Provides `GraphServiceClient` for new directory service |
+| DI registration | `SharepointToolbox/App.xaml.cs` (lines 73-163) | Register new BrandingRepository, BrandingService, GraphUserDirectoryService |
+| Profile deletion UI | `SharepointToolbox/ViewModels/ProfileManagementViewModel.cs` | Update deletion confirmation message to mention logo |
@@ -0,0 +1,530 @@
+# Phase 10: Branding Data Foundation - Research
+
+**Researched:** 2026-04-08
+**Domain:** C# WPF / .NET 10 — JSON persistence, image validation, Microsoft Graph SDK pagination
+**Confidence:** HIGH
+
+## Summary
+
+Phase 10 is a pure infrastructure phase: no UI, no new NuGet packages. It introduces three new models (`LogoData`, `BrandingSettings`, plus extends `TenantProfile`), two repositories (`BrandingRepository` mirroring `SettingsRepository`), two services (`BrandingService` for validation/compression, `GraphUserDirectoryService` for paginated Graph enumeration), and registration of those in `App.xaml.cs`. All work is additive — nothing in the existing stack is removed or renamed.
+
+The central technical challenge splits into two independent tracks:
+1. **Logo storage track:** Image format detection from magic bytes, silent compression using `System.Drawing.Common` (available via WPF's `PresentationCore`/`System.Drawing.Common` BCL subset on net10.0-windows), base64 serialization in JSON.
+2. **Graph directory track:** `PageIterator<User, UserCollectionResponse>` from Microsoft.Graph 5.x following `@odata.nextLink` until exhausted, with `CancellationToken` threading throughout.
+
+Both tracks fit the existing patterns precisely. The repository uses `SemaphoreSlim(1,1)` + write-then-move. The Graph service clones `GraphUserSearchService` structure while substituting `PageIterator` for a one-shot `GetAsync`. No configuration, no new packages, no breaking changes.
+
+**Primary recommendation:** Implement in order — models first, then repository, then services, then DI registration, then update `ProfileManagementViewModel.DeleteAsync` warning message. Tests mirror the `SettingsServiceTests` and `ProfileServiceTests` patterns already present.
+
+---
+
+<user_constraints>
+## User Constraints (from CONTEXT.md)
+
+### Locked Decisions
+| Decision | Value |
+|---|---|
+| Logo storage format | Base64 strings in JSON (not file paths) |
+| MSP logo location | `BrandingSettings.cs` model → `branding.json` |
+| Client logo location | On `TenantProfile` model (per-tenant) |
+| File path after import | Discarded — only base64 persists |
+| SVG support | Rejected (XSS risk) — PNG/JPG only |
+| User directory service | New `GraphUserDirectoryService`, separate from `GraphUserSearchService` |
+| Directory auto-load | No — explicit "Load Directory" button required |
+| New NuGet packages | None — existing stack covers everything |
+| Export service signature | Optional `ReportBranding? branding = null` parameter on existing export methods |
+
+### Claude's Discretion
+- No discretion areas defined for Phase 10 — all decisions locked.
+
+### Deferred Ideas (OUT OF SCOPE)
+- Logo preview in Settings UI (Phase 12)
+- Auto-pull client logo from Entra branding API (Phase 11/12)
+- Report header layout with logos side-by-side (Phase 11)
+- "Load Directory" button placement decision (Phase 14)
+- Session-scoped directory cache (UDIR-F01, deferred)
+</user_constraints>
+
+---
+
+<phase_requirements>
+## Phase Requirements
+
+| ID | Description | Research Support |
+|----|-------------|-----------------|
+| BRAND-01 | User can import an MSP logo in application settings (global, persisted across sessions) | `BrandingSettings` model + `BrandingRepository` (mirrors `SettingsRepository`) + `BrandingService.ImportLogoAsync` |
+| BRAND-03 | User can import a client logo per tenant profile | `LogoData? ClientLogo` property on `TenantProfile` + `ProfileRepository` already handles serialization; `BrandingService.ImportLogoAsync` reused |
+| BRAND-06 | Logo import validates format (PNG/JPG) and enforces 512 KB size limit | Magic byte detection (PNG: `89 50 4E 47`, JPEG: `FF D8 FF`) + auto-compress via `System.Drawing`/`BitmapEncoder` if > 512 KB |
+</phase_requirements>
+
+---
+
+## Standard Stack
+
+### Core (all already present — zero new installs)
+| Library | Version | Purpose | Why Standard |
+|---------|---------|---------|--------------|
+| `System.Text.Json` | BCL (net10.0) | JSON serialization of models | Already used in all repositories |
+| `System.Drawing.Common` | BCL (net10.0-windows) | Image load, resize, re-encode for compression | Available on Windows via `UseWPF=true`; no extra package |
+| `Microsoft.Graph` | 5.74.0 (already in csproj) | Graph SDK for user enumeration | Already used by `GraphUserSearchService` |
+| `Microsoft.Identity.Client` | 4.83.3 (already in csproj) | Token acquisition via `GraphClientFactory` | Already used |
+| `CommunityToolkit.Mvvm` | 8.4.2 (already in csproj) | `[ObservableProperty]` for ViewModels — not used in Phase 10 directly, but referenced by `ProfileManagementViewModel` | Already used |
+
+### No New Packages
+All capabilities are covered by the existing stack. Confirmed in CONTEXT.md locked decisions and csproj inspection.
+
+## Architecture Patterns
+
+### Recommended Project Structure (new files only)
+
+```
+SharepointToolbox/
+├── Core/
+│   └── Models/
+│       ├── LogoData.cs               -- record LogoData(string Base64, string MimeType)
+│       └── BrandingSettings.cs       -- class BrandingSettings { LogoData? MspLogo; }
+├── Infrastructure/
+│   └── Persistence/
+│       └── BrandingRepository.cs     -- clone of SettingsRepository<BrandingSettings>
+├── Services/
+│   ├── IBrandingService.cs           -- ImportLogoAsync, ClearLogoAsync
+│   ├── BrandingService.cs            -- validates magic bytes, compresses, returns LogoData
+│   ├── IGraphUserDirectoryService.cs -- GetUsersAsync with PageIterator
+│   └── GraphUserDirectoryService.cs  -- PageIterator pagination
+
+SharepointToolbox.Tests/
+└── Services/
+    ├── BrandingServiceTests.cs       -- magic bytes, compression, rejection
+    └── GraphUserDirectoryServiceTests.cs  -- pagination (mocked PageIterator or direct list)
+```
+
+### Pattern 1: Repository (write-then-move with SemaphoreSlim)
+
+Exact clone of `SettingsRepository` with `BrandingSettings` substituted for `AppSettings`. No deviations.
+
+```csharp
+// Source: SharepointToolbox/Infrastructure/Persistence/SettingsRepository.cs (existing)
+public class BrandingRepository
+{
+    private readonly string _filePath;
+    private readonly SemaphoreSlim _writeLock = new(1, 1);
+
+    public async Task<BrandingSettings> LoadAsync()
+    {
+        if (!File.Exists(_filePath))
+            return new BrandingSettings();
+        // ... File.ReadAllTextAsync + JsonSerializer.Deserialize<BrandingSettings> ...
+    }
+
+    public async Task SaveAsync(BrandingSettings settings)
+    {
+        await _writeLock.WaitAsync();
+        try
+        {
+            var json = JsonSerializer.Serialize(settings,
+                new JsonSerializerOptions { WriteIndented = true, PropertyNamingPolicy = JsonNamingPolicy.CamelCase });
+            var tmpPath = _filePath + ".tmp";
+            // ... write to tmp, validate round-trip, File.Move(tmp, _filePath, overwrite: true) ...
+        }
+        finally { _writeLock.Release(); }
+    }
+}
+```
+
+### Pattern 2: LogoData record — shared by MSP and client logos
+
+```csharp
+// Source: CONTEXT.md §1 Logo Metadata Model
+namespace SharepointToolbox.Core.Models;
+
+public record LogoData(string Base64, string MimeType);
+// MimeType is "image/png" or "image/jpeg" — determined at import time from magic bytes
+// Usage in HTML: $"data:{MimeType};base64,{Base64}"
+```
+
+### Pattern 3: BrandingSettings model
+
+```csharp
+namespace SharepointToolbox.Core.Models;
+
+public class BrandingSettings
+{
+    public LogoData? MspLogo { get; set; }
+}
+```
+
+### Pattern 4: TenantProfile extension
+
+```csharp
+// Extend existing TenantProfile — additive, no breaking change
+public class TenantProfile
+{
+    public string Name { get; set; } = string.Empty;
+    public string TenantUrl { get; set; } = string.Empty;
+    public string ClientId { get; set; } = string.Empty;
+    public LogoData? ClientLogo { get; set; }   // NEW — nullable, ignored when null in JSON
+}
+```
+
+`ProfileRepository` needs no code change — `System.Text.Json` serializes the new nullable property automatically. Existing profiles JSON without `clientLogo` deserializes with `null` (forward-compatible).
+
+### Pattern 5: Magic byte validation + compression in BrandingService
+
+```csharp
+// Source: CONTEXT.md §2 Logo Validation & Compression
+private static readonly byte[] PngSignature = { 0x89, 0x50, 0x4E, 0x47 };
+private static readonly byte[] JpegSignature = { 0xFF, 0xD8, 0xFF };
+
+private static string? DetectMimeType(byte[] header)
+{
+    if (header.Length >= 4 && header.Take(4).SequenceEqual(PngSignature)) return "image/png";
+    if (header.Length >= 3 && header.Take(3).SequenceEqual(JpegSignature)) return "image/jpeg";
+    return null;
+}
+
+public async Task<LogoData> ImportLogoAsync(string filePath)
+{
+    var bytes = await File.ReadAllBytesAsync(filePath);
+    var mimeType = DetectMimeType(bytes)
+        ?? throw new InvalidDataException("File format is not PNG or JPG. Only PNG and JPG are accepted.");
+
+    if (bytes.Length > 512 * 1024)
+        bytes = CompressToLimit(bytes, mimeType, maxBytes: 512 * 1024);
+
+    return new LogoData(Convert.ToBase64String(bytes), mimeType);
+}
+```
+
+For compression, use `System.Drawing.Bitmap` (available on net10.0-windows) to resize to max 300×300px and re-encode at reduced quality using `System.Drawing.Imaging.ImageCodecInfo`/`EncoderParameters`. Keep original format.
+
+### Pattern 6: GraphUserDirectoryService with PageIterator
+
+Microsoft.Graph 5.x includes `PageIterator<TEntity, TCollectionPage>` in `Microsoft.Graph.Core`. Pattern from Graph SDK docs:
+
+```csharp
+// Source: Microsoft.Graph 5.x SDK — PageIterator pattern
+public async Task<IReadOnlyList<GraphDirectoryUser>> GetUsersAsync(
+    string clientId,
+    CancellationToken ct = default)
+{
+    var graphClient = await _graphClientFactory.CreateClientAsync(clientId, ct);
+    var results = new List<GraphDirectoryUser>();
+
+    var response = await graphClient.Users.GetAsync(config =>
+    {
+        config.QueryParameters.Filter = "accountEnabled eq true and userType eq 'Member'";
+        config.QueryParameters.Select = new[] { "displayName", "userPrincipalName", "mail", "department", "jobTitle" };
+        config.QueryParameters.Top = 999;
+    }, ct);
+
+    if (response is null) return results;
+
+    var pageIterator = PageIterator<User, UserCollectionResponse>.CreatePageIterator(
+        graphClient,
+        response,
+        user =>
+        {
+            results.Add(new GraphDirectoryUser(
+                user.DisplayName ?? user.UserPrincipalName ?? string.Empty,
+                user.UserPrincipalName ?? string.Empty,
+                user.Mail,
+                user.Department,
+                user.JobTitle));
+            return true; // continue iteration
+        });
+
+    await pageIterator.IterateAsync(ct);
+    return results;
+}
+```
+
+`PageIterator` requires `Microsoft.Graph.Core` which is a transitive dependency of `Microsoft.Graph` 5.x — already present.
+
+**No `ConsistencyLevel: eventual` needed** for the `$filter` query with `accountEnabled` and `userType` — these are standard properties, not advanced queries requiring `$count`. (Unlike the search service which uses `startsWith` and requires `ConsistencyLevel`.)
+
+### Pattern 7: DI registration (App.xaml.cs)
+
+```csharp
+// Phase 10: Branding Data Foundation
+services.AddSingleton(_ => new BrandingRepository(Path.Combine(appData, "branding.json")));
+services.AddSingleton<BrandingService>();
+services.AddTransient<IGraphUserDirectoryService, GraphUserDirectoryService>();
+```
+
+`BrandingRepository` is Singleton (same rationale as `ProfileRepository` and `SettingsRepository` — single file, shared lock). `BrandingService` is Singleton (stateless after construction, depends on singleton repository). `GraphUserDirectoryService` is Transient (per-tenant call, stateless).
+
+### Pattern 8: ProfileManagementViewModel deletion message update
+
+In `ProfileManagementViewModel.DeleteAsync()`, the existing confirmation flow has no dialog — it directly calls `_profileService.DeleteProfileAsync`. The update per CONTEXT.md is to augment the confirmation message (when that dialog exists) to mention logo removal. However, Phase 10 does not add a confirmation dialog — that is the caller's concern (View layer, Phase 12). The ViewModel update is to expose information about whether a profile has a logo, enabling Phase 12's View to conditionally show the warning.
+
+```csharp
+// Add a computed property to support the deletion warning in Phase 12
+// This is the minimal Phase 10 change:
+// TenantProfile.ClientLogo != null → the confirmation dialog (Phase 12) reads this
+```
+
+The actual deletion behavior is unchanged: deleting the profile JSON entry automatically drops the embedded `clientLogo` field. No orphaned files exist.
+
+### Anti-Patterns to Avoid
+
+- **Do not store the file path in JSON** — only base64 + MIME type. File path is discarded immediately after reading bytes.
+- **Do not use file extension for format detection** — always read magic bytes from the byte array.
+- **Do not use `$search` or `$count` on the directory query** — `PageIterator` with `$filter=accountEnabled eq true and userType eq 'Member'` does not require `ConsistencyLevel: eventual`.
+- **Do not create a new interface for BrandingRepository** — `SettingsRepository` has no interface either; only services get interfaces.
+- **Do not add `[ObservableProperty]` to `LogoData`** — it is a plain record used in persistence layer; ViewModel bindings come in Phase 11-12.
+
+## Don't Hand-Roll
+
+| Problem | Don't Build | Use Instead | Why |
+|---------|-------------|-------------|-----|
+| JSON pagination follow-up | Manual `@odata.nextLink` string parsing loop | `PageIterator<User, UserCollectionResponse>` | SDK handles retry, null checks, async iteration natively |
+| Image format detection | File extension check | Magic byte read on first 4 bytes | Extensions are user-controlled and unreliable |
+| Atomic file write | Direct `File.WriteAllText` | Write to `.tmp`, validate, `File.Move(overwrite:true)` | Crash during write leaves corrupted JSON; pattern already proven in all repos |
+| Concurrency guard | `lock(obj)` | `SemaphoreSlim(1,1)` | Async-safe; `lock` cannot be awaited |
+| Base64 encoding | Manual byte-to-char loop | `Convert.ToBase64String(bytes)` | BCL, zero allocation path, no edge cases |
+
+## Common Pitfalls
+
+### Pitfall 1: `System.Drawing` availability on net10.0-windows
+**What goes wrong:** `System.Drawing.Common` is available on Windows (the project already targets `net10.0-windows` with `UseWPF=true`) but would throw `PlatformNotSupportedException` on Linux/macOS runtimes.
+**Why it happens:** .NET 6+ restricted `System.Drawing.Common` to Windows-only by default.
+**How to avoid:** This project is Windows-only (WinExe, UseWPF=true) so no risk. No guard needed.
+**Warning signs:** CI on Linux — not applicable here.
+
+### Pitfall 2: `PageIterator.IterateAsync` does not accept `CancellationToken` directly in Graph SDK 5.x
+**What goes wrong:** `PageIterator.IterateAsync()` in Microsoft.Graph 5.x overloads — the token must be passed when calling `CreatePageIterator`, and the iteration callback must check cancellation manually or the token goes to `IterateAsync(ct)` if the overload exists.
+**Why it happens:** API surface changed between SDK versions.
+**How to avoid:** Check token inside the callback: `if (ct.IsCancellationRequested) return false;` stops iteration. Also pass `ct` to the initial `GetAsync` call.
+**Warning signs:** Long-running enumeration that ignores cancellation requests.
+
+### Pitfall 3: Deserialization of `LogoData` record with `System.Text.Json`
+**What goes wrong:** C# records with positional constructors may not deserialize correctly with `System.Text.Json` unless the property names match constructor parameter names exactly (case-insensitive with `PropertyNameCaseInsensitive = true`) or a `[JsonConstructor]` attribute is present.
+**Why it happens:** Positional record constructor parameters are `base64` and `mimeType` (camelCase) while JSON uses `PropertyNamingPolicy.CamelCase`.
+**How to avoid:** Use a class with `{ get; set; }` properties OR add `[JsonConstructor]` to the positional record constructor. Simpler: make `LogoData` a class with init setters or a non-positional record with `{ get; init; }` properties.
+
+```csharp
+// SAFE version — class-style record with init setters:
+public record LogoData
+{
+    public string Base64 { get; init; } = string.Empty;
+    public string MimeType { get; init; } = string.Empty;
+}
+```
+
+### Pitfall 4: Large base64 string bloating profiles.json
+**What goes wrong:** A 512 KB logo becomes ~682 KB of base64 text. Per-profile, this is manageable. However, `ProfileRepository.LoadAsync` loads ALL profiles at once — 20 tenants with logos = ~14 MB in memory per load.
+**Why it happens:** All profiles are stored in a single JSON array.
+**How to avoid:** Phase 10 does not address this (deferred); the 512 KB cap keeps it bounded. Document as known limitation.
+**Warning signs:** Not a Phase 10 concern — flag for future phases if profile count grows large.
+
+### Pitfall 5: `File.Move` with `overwrite: true` not available on all .NET versions
+**What goes wrong:** `File.Move(src, dst, overwrite: true)` was added in .NET 3.0. On older frameworks this throws.
+**Why it happens:** Legacy API surface.
+**How to avoid:** Not applicable — project targets net10.0. Use freely.
+
+### Pitfall 6: Graph $filter without ConsistencyLevel on advanced queries
+**What goes wrong:** The search service uses `startsWith()` which requires `ConsistencyLevel: eventual + $count=true`. If the directory service accidentally includes `$count` or `$search`, it needs the header too.
+**Why it happens:** Copy-paste from `GraphUserSearchService` without removing the `ConsistencyLevel` header.
+**How to avoid:** The directory filter `accountEnabled eq true and userType eq 'Member'` is a standard equality filter — does NOT require `ConsistencyLevel: eventual`. Do not copy the header from `GraphUserSearchService`.
+
+## Code Examples
+
+### Magic Byte Detection
+```csharp
+// Source: CONTEXT.md §2 Logo Validation; confirmed against PNG/JPEG specs
+private static readonly byte[] PngMagic  = { 0x89, 0x50, 0x4E, 0x47 };
+private static readonly byte[] JpegMagic = { 0xFF, 0xD8, 0xFF };
+
+private static string? DetectMimeType(ReadOnlySpan<byte> header)
+{
+    if (header.Length >= 4 && header[..4].SequenceEqual(PngMagic))  return "image/png";
+    if (header.Length >= 3 && header[..3].SequenceEqual(JpegMagic)) return "image/jpeg";
+    return null;
+}
+```
+
+### Compression via System.Drawing (net10.0-windows)
+```csharp
+// Source: BCL System.Drawing.Common — Windows-only, safe here
+private static byte[] CompressImage(byte[] original, string mimeType, int maxBytes)
+{
+    using var ms = new MemoryStream(original);
+    using var bitmap = new System.Drawing.Bitmap(ms);
+
+    // Scale down proportionally to max 300px
+    int w = bitmap.Width, h = bitmap.Height;
+    if (w > 300 || h > 300)
+    {
+        double scale = Math.Min(300.0 / w, 300.0 / h);
+        w = (int)(w * scale);
+        h = (int)(h * scale);
+    }
+
+    using var resized = new System.Drawing.Bitmap(bitmap, w, h);
+
+    // Re-encode
+    var codec = System.Drawing.Imaging.ImageCodecInfo.GetImageEncoders()
+        .First(c => c.MimeType == mimeType);
+    var encoderParams = new System.Drawing.Imaging.EncoderParameters(1);
+    encoderParams.Param[0] = new System.Drawing.Imaging.EncoderParameter(
+        System.Drawing.Imaging.Encoder.Quality, 75L);
+
+    using var output = new MemoryStream();
+    resized.Save(output, codec, encoderParams);
+    return output.ToArray();
+}
+```
+
+### PageIterator pattern (Microsoft.Graph 5.x)
+```csharp
+// Source: Microsoft.Graph 5.x SDK pattern; PageIterator<TEntity, TCollectionPage>
+var pageIterator = PageIterator<User, UserCollectionResponse>.CreatePageIterator(
+    graphClient,
+    firstPage,
+    user =>
+    {
+        if (ct.IsCancellationRequested) return false;
+        results.Add(MapUser(user));
+        return true;
+    });
+
+await pageIterator.IterateAsync(ct);
+```
+
+### GraphDirectoryUser result record
+```csharp
+// New record for Phase 10 — placed in Services/ or Core/Models/
+public record GraphDirectoryUser(
+    string DisplayName,
+    string UserPrincipalName,
+    string? Mail,
+    string? Department,
+    string? JobTitle);
+```
+
+### JSON shape of branding.json
+```json
+{
+  "mspLogo": {
+    "base64": "iVBORw0KGgo...",
+    "mimeType": "image/png"
+  }
+}
+```
+
+### JSON shape of profiles.json (after Phase 10)
+```json
+{
+  "profiles": [
+    {
+      "name": "Contoso",
+      "tenantUrl": "https://contoso.sharepoint.com",
+      "clientId": "...",
+      "clientLogo": {
+        "base64": "/9j/4AAQ...",
+        "mimeType": "image/jpeg"
+      }
+    },
+    {
+      "name": "Fabrikam",
+      "tenantUrl": "https://fabrikam.sharepoint.com",
+      "clientId": "...",
+      "clientLogo": null
+    }
+  ]
+}
+```
+
+## State of the Art
+
+| Old Approach | Current Approach | When Changed | Impact |
+|--------------|------------------|--------------|--------|
+| Manual `@odata.nextLink` loop | `PageIterator<T, TPage>` | Microsoft.Graph 5.x (current) | Handles backoff, null-safety, async natively |
+| `System.Drawing` everywhere | `System.Drawing` Windows-only | .NET 6 | No impact here — Windows-only project |
+| Class-based Graph response models | Record/POCO `Value` collections | Microsoft.Graph 5.x | `response.Value` is `List<User>?` |
+
+**Deprecated/outdated:**
+- `Microsoft.Graph.Beta` namespace: not needed here — standard `/v1.0/users` endpoint sufficient
+- `IAuthenticationProvider` (old Graph SDK): replaced by `BaseBearerTokenAuthenticationProvider` — already correct in `GraphClientFactory`
+
+## Open Questions
+
+1. **CancellationToken in PageIterator.IterateAsync — exact overload in Graph SDK 5.74.0**
+   - What we know: `PageIterator` exists in `Microsoft.Graph.Core`; `IterateAsync` exists. Token passing confirmed in SDK samples.
+   - What's unclear: Whether `IterateAsync(CancellationToken)` overload exists in 5.74.0 or only the parameterless version.
+   - Recommendation: Check when implementing. If parameterless only, use `ct.IsCancellationRequested` inside callback to return `false` and stop iteration. Either approach works correctly.
+
+2. **$filter=accountEnabled eq true and userType eq 'Member' — verified against real tenant?**
+   - STATE.md flags this as a pending todo: "Confirm `$filter=accountEnabled eq true and userType eq 'Member'` behavior without `ConsistencyLevel: eventual` against a real tenant before Phase 13 planning."
+   - Phase 10 implements the service; Phase 13 will exercise the filter in the ViewModel. The pending verification is appropriate for Phase 13.
+   - Recommendation: Implement the filter as specified. Flag in `GraphUserDirectoryService` with a comment noting the pending verification.
+
+---
+
+## Validation Architecture
+
+### Test Framework
+| Property | Value |
+|----------|-------|
+| Framework | xUnit 2.9.3 + Moq 4.20.72 |
+| Config file | `SharepointToolbox.Tests/SharepointToolbox.Tests.csproj` |
+| Quick run command | `dotnet test --filter "Category=Unit" --no-build` |
+| Full suite command | `dotnet test` |
+
+### Phase Requirements → Test Map
+
+| Req ID | Behavior | Test Type | Automated Command | File Exists? |
+|--------|----------|-----------|-------------------|-------------|
+| BRAND-01 | MSP logo saved to `branding.json` and reloaded correctly | unit | `dotnet test --filter "FullyQualifiedName~BrandingServiceTests" --no-build` | ❌ Wave 0 |
+| BRAND-01 | `BrandingRepository` round-trips `BrandingSettings` with `MspLogo` | unit | `dotnet test --filter "FullyQualifiedName~BrandingRepositoryTests" --no-build` | ❌ Wave 0 |
+| BRAND-03 | `TenantProfile.ClientLogo` serializes/deserializes in `ProfileRepository` | unit | `dotnet test --filter "FullyQualifiedName~ProfileServiceTests" --no-build` | ✅ (extend existing) |
+| BRAND-06 | PNG file accepted, returns `image/png` MIME | unit | `dotnet test --filter "FullyQualifiedName~BrandingServiceTests" --no-build` | ❌ Wave 0 |
+| BRAND-06 | JPEG file accepted, returns `image/jpeg` MIME | unit | `dotnet test --filter "FullyQualifiedName~BrandingServiceTests" --no-build` | ❌ Wave 0 |
+| BRAND-06 | BMP file rejected with descriptive error | unit | `dotnet test --filter "FullyQualifiedName~BrandingServiceTests" --no-build` | ❌ Wave 0 |
+| BRAND-06 | File > 512 KB is auto-compressed (output ≤ 512 KB) | unit | `dotnet test --filter "FullyQualifiedName~BrandingServiceTests" --no-build` | ❌ Wave 0 |
+| BRAND-06 | File ≤ 512 KB is not modified | unit | `dotnet test --filter "FullyQualifiedName~BrandingServiceTests" --no-build` | ❌ Wave 0 |
+| (UDIR-02 infra) | `GetUsersAsync` follows all pages until exhausted | unit | `dotnet test --filter "FullyQualifiedName~GraphUserDirectoryServiceTests" --no-build` | ❌ Wave 0 |
+| (UDIR-02 infra) | `GetUsersAsync` respects `CancellationToken` mid-iteration | unit | `dotnet test --filter "FullyQualifiedName~GraphUserDirectoryServiceTests" --no-build` | ❌ Wave 0 |
+
+### Sampling Rate
+- **Per task commit:** `dotnet test --filter "Category=Unit" --no-build`
+- **Per wave merge:** `dotnet test`
+- **Phase gate:** Full suite green before `/gsd:verify-work`
+
+### Wave 0 Gaps
+- [ ] `SharepointToolbox.Tests/Services/BrandingServiceTests.cs` — covers BRAND-06 + BRAND-01 import logic
+- [ ] `SharepointToolbox.Tests/Services/BrandingRepositoryTests.cs` — covers BRAND-01 persistence
+- [ ] `SharepointToolbox.Tests/Services/GraphUserDirectoryServiceTests.cs` — covers UDIR-02 infrastructure
+
+*(Extend existing `ProfileServiceTests.cs` to verify `ClientLogo` round-trip — covers BRAND-03)*
+
+---
+
+## Sources
+
+### Primary (HIGH confidence)
+- Codebase inspection — `SettingsRepository.cs`, `ProfileRepository.cs`, `GraphUserSearchService.cs`, `GraphClientFactory.cs`, `App.xaml.cs`, `TenantProfile.cs`, `AppSettings.cs`
+- `SharepointToolbox.csproj` — confirms Microsoft.Graph 5.74.0, no System.Drawing explicit reference needed (net10.0-windows)
+- `SharepointToolbox.Tests.csproj` — confirms xUnit 2.9.3, Moq 4.20.72 test stack
+- `10-CONTEXT.md` — locked decisions, compression strategy, magic byte specs, model shapes
+
+### Secondary (MEDIUM confidence)
+- Microsoft.Graph 5.x SDK architecture — `PageIterator<T, TPage>` pattern confirmed in Graph SDK source and documentation; version 5.74.0 is current
+- `System.Drawing.Common` Windows availability — confirmed by .NET documentation: available on Windows, restricted on non-Windows since .NET 6
+
+### Tertiary (LOW confidence)
+- `PageIterator.IterateAsync(CancellationToken)` overload availability in 5.74.0 specifically — needs compile-time verification
+
+---
+
+## Metadata
+
+**Confidence breakdown:**
+- Standard stack: HIGH — confirmed from csproj; zero new packages
+- Architecture: HIGH — all patterns are direct clones of existing code in the repo
+- Magic byte detection: HIGH — PNG/JPEG signatures are stable specs
+- PageIterator pattern: MEDIUM — SDK version-specific overload needs verification at implementation time
+- Pitfalls: HIGH — identified from codebase inspection and known .NET behaviors
+
+**Research date:** 2026-04-08
+**Valid until:** 2026-05-08 (stable domain — Microsoft.Graph minor versions change rarely)
@@ -0,0 +1,79 @@
+---
+phase: 10
+slug: branding-data-foundation
+status: draft
+nyquist_compliant: false
+wave_0_complete: false
+created: 2026-04-08
+---
+
+# Phase 10 — Validation Strategy
+
+> Per-phase validation contract for feedback sampling during execution.
+
+---
+
+## Test Infrastructure
+
+| Property | Value |
+|----------|-------|
+| **Framework** | xUnit 2.9.3 + Moq 4.20.72 |
+| **Config file** | `SharepointToolbox.Tests/SharepointToolbox.Tests.csproj` |
+| **Quick run command** | `dotnet test --filter "Category=Unit" --no-build` |
+| **Full suite command** | `dotnet test` |
+| **Estimated runtime** | ~15 seconds |
+
+---
+
+## Sampling Rate
+
+- **After every task commit:** Run `dotnet test --filter "Category=Unit" --no-build`
+- **After every plan wave:** Run `dotnet test`
+- **Before `/gsd:verify-work`:** Full suite must be green
+- **Max feedback latency:** 15 seconds
+
+---
+
+## Per-Task Verification Map
+
+| Task ID | Plan | Wave | Requirement | Test Type | Automated Command | File Exists | Status |
+|---------|------|------|-------------|-----------|-------------------|-------------|--------|
+| 10-01-01 | 01 | 1 | BRAND-01 | unit | `dotnet test --filter "FullyQualifiedName~BrandingRepositoryTests" --no-build` | ❌ W0 | ⬜ pending |
+| 10-01-02 | 01 | 1 | BRAND-06 | unit | `dotnet test --filter "FullyQualifiedName~BrandingServiceTests" --no-build` | ❌ W0 | ⬜ pending |
+| 10-01-03 | 01 | 1 | BRAND-03 | unit | `dotnet test --filter "FullyQualifiedName~ProfileServiceTests" --no-build` | ✅ extend | ⬜ pending |
+| 10-02-01 | 02 | 1 | UDIR-02 | unit | `dotnet test --filter "FullyQualifiedName~GraphUserDirectoryServiceTests" --no-build` | ❌ W0 | ⬜ pending |
+
+*Status: ⬜ pending · ✅ green · ❌ red · ⚠️ flaky*
+
+---
+
+## Wave 0 Requirements
+
+- [ ] `SharepointToolbox.Tests/Services/BrandingRepositoryTests.cs` — stubs for BRAND-01 persistence round-trip
+- [ ] `SharepointToolbox.Tests/Services/BrandingServiceTests.cs` — stubs for BRAND-06 magic bytes, compression, rejection
+- [ ] `SharepointToolbox.Tests/Services/GraphUserDirectoryServiceTests.cs` — stubs for UDIR-02 pagination
+- [ ] Extend `SharepointToolbox.Tests/Services/ProfileServiceTests.cs` — add BRAND-03 `ClientLogo` round-trip test
+
+*Existing infrastructure covers test framework setup.*
+
+---
+
+## Manual-Only Verifications
+
+| Behavior | Requirement | Why Manual | Test Instructions |
+|----------|-------------|------------|-------------------|
+| MSP logo survives app restart | BRAND-01 | Requires full app lifecycle (start, import, close, reopen) | 1. Run app, import MSP logo 2. Close app 3. Reopen app 4. Verify logo still present in branding.json |
+| Client logo isolated between tenants | BRAND-03 | Requires multi-profile JSON inspection | 1. Import logo for Tenant A 2. Verify Tenant B profile has no logo field 3. Delete Tenant A logo 4. Verify Tenant B unaffected |
+
+---
+
+## Validation Sign-Off
+
+- [ ] All tasks have `<automated>` verify or Wave 0 dependencies
+- [ ] Sampling continuity: no 3 consecutive tasks without automated verify
+- [ ] Wave 0 covers all MISSING references
+- [ ] No watch-mode flags
+- [ ] Feedback latency < 15s
+- [ ] `nyquist_compliant: true` set in frontmatter
+
+**Approval:** pending
@@ -0,0 +1,150 @@
+---
+phase: 10-branding-data-foundation
+verified: 2026-04-08T12:00:00Z
+status: passed
+score: 8/8 must-haves verified
+re_verification: false
+---
+
+# Phase 10: Branding Data Foundation Verification Report
+
+**Phase Goal:** The application can store, validate, and retrieve MSP and client logos as portable base64 strings in JSON, and can enumerate a full tenant user list with pagination.
+**Verified:** 2026-04-08
+**Status:** PASSED
+**Re-verification:** No — initial verification
+
+---
+
+## Goal Achievement
+
+### Observable Truths
+
+| # | Truth | Status | Evidence |
+|---|-------|--------|----------|
+| 1 | An MSP logo imported as PNG or JPG is persisted as base64 in branding.json and survives round-trip | VERIFIED | `BrandingService.ImportLogoAsync` + `SaveMspLogoAsync` + `BrandingRepository.SaveAsync/LoadAsync`; 3 tests confirm round-trip |
+| 2 | A client logo imported per tenant profile is persisted as base64 inside the profile JSON | VERIFIED | `TenantProfile.ClientLogo` property added; serialization/deserialization confirmed by 2 `BrandingRepositoryTests` |
+| 3 | A file that is not PNG/JPG (e.g., BMP) is rejected with a descriptive error message | VERIFIED | `DetectMimeType` throws `InvalidDataException("File format is not PNG or JPG…")`; test `ImportLogoAsync_BmpFile_ThrowsInvalidDataExceptionMentioningPngAndJpg` passes |
+| 4 | A file larger than 512 KB is silently compressed to fit under the limit | VERIFIED | `CompressToLimit` two-pass WPF imaging (300x300@75 then 200x200@50); test `ImportLogoAsync_FileOver512KB_ReturnsCompressedUnder512KB` passes |
+| 5 | A file under 512 KB is stored without modification | VERIFIED | No compression branch taken; test `ImportLogoAsync_FileUnder512KB_ReturnOriginalBytesUnmodified` passes confirming byte-for-byte identity |
+| 6 | `GetUsersAsync` returns all enabled member users following `@odata.nextLink` until exhausted | VERIFIED | `PageIterator<User, UserCollectionResponse>` used; `IterateAsync` called; integration-level pagination tests skipped with documented rationale (PageIterator internals not mockable) |
+| 7 | `GetUsersAsync` respects CancellationToken and stops iteration when cancelled | VERIFIED | `ct.IsCancellationRequested` checked inside callback; `return false` stops PageIterator; integration test skipped with documented rationale |
+| 8 | Each returned user includes DisplayName, UserPrincipalName, Mail, Department, and JobTitle | VERIFIED | `MapUser` maps all 5 fields with null-fallback chain; 5 `MapUser` unit tests pass covering all field combinations |
+
+**Score:** 8/8 truths verified
+
+---
+
+## Required Artifacts
+
+### Plan 01 Artifacts
+
+| Artifact | Expected | Status | Details |
+|----------|----------|--------|---------|
+| `SharepointToolbox/Core/Models/LogoData.cs` | Shared logo record with Base64 and MimeType init properties | VERIFIED | Non-positional record; both properties with `get; init;`; 7 lines |
+| `SharepointToolbox/Core/Models/BrandingSettings.cs` | MSP logo wrapper model | VERIFIED | `LogoData? MspLogo { get; set; }` present |
+| `SharepointToolbox/Core/Models/TenantProfile.cs` | Client logo property on existing profile model | VERIFIED | `LogoData? ClientLogo { get; set; }` added additively; all 3 original properties retained |
+| `SharepointToolbox/Infrastructure/Persistence/BrandingRepository.cs` | JSON persistence with write-then-replace safety | VERIFIED | `SemaphoreSlim(1,1)`, `.tmp` write-then-validate-then-move pattern, `JsonDocument.Parse` validation before `File.Move` |
+| `SharepointToolbox/Services/BrandingService.cs` | Logo import with magic byte validation and auto-compression | VERIFIED | `ImportLogoAsync`, `SaveMspLogoAsync`, `ClearMspLogoAsync`, `GetMspLogoAsync` all implemented; WPF imaging compression |
+| `SharepointToolbox.Tests/Services/BrandingRepositoryTests.cs` | Unit tests for validation, compression, rejection | VERIFIED | 5 tests; IDisposable + temp file pattern; all pass |
+| `SharepointToolbox.Tests/Services/BrandingServiceTests.cs` | Unit tests for repository round-trip | VERIFIED | 9 tests (224 lines); IDisposable + temp file pattern; all pass |
+
+### Plan 02 Artifacts
+
+| Artifact | Expected | Status | Details |
+|----------|----------|--------|---------|
+| `SharepointToolbox/Core/Models/GraphDirectoryUser.cs` | Result record for directory enumeration | VERIFIED | Positional record with all 5 fields |
+| `SharepointToolbox/Services/IGraphUserDirectoryService.cs` | Interface for directory enumeration | VERIFIED | `GetUsersAsync(clientId, IProgress<int>?, CancellationToken)` declared |
+| `SharepointToolbox/Services/GraphUserDirectoryService.cs` | PageIterator-based Graph user enumeration | VERIFIED | `PageIterator<User, UserCollectionResponse>.CreatePageIterator` used; `IterateAsync` called |
+| `SharepointToolbox.Tests/Services/GraphUserDirectoryServiceTests.cs` | Unit tests for directory service | VERIFIED | 9 tests (5 pass, 4 skipped with documented rationale); 150 lines |
+
+### Plan 03 Artifacts
+
+| Artifact | Expected | Status | Details |
+|----------|----------|--------|---------|
+| `SharepointToolbox/App.xaml.cs` | DI registration for Phase 10 services | VERIFIED | Phase 10 block at lines 81-84 |
+
+---
+
+## Key Link Verification
+
+### Plan 01 Key Links
+
+| From | To | Via | Status | Details |
+|------|----|-----|--------|---------|
+| `BrandingService.cs` | `BrandingRepository.cs` | Constructor injection | VERIFIED | Constructor takes `BrandingRepository _repository`; all CRUD methods call `_repository.LoadAsync/SaveAsync` |
+| `BrandingService.cs` | `LogoData.cs` | Return type | VERIFIED | `ImportLogoAsync` returns `Task<LogoData>`; `new LogoData { Base64=…, MimeType=… }` constructed |
+| `BrandingSettings.cs` | `LogoData.cs` | Property type | VERIFIED | `LogoData? MspLogo { get; set; }` |
+| `TenantProfile.cs` | `LogoData.cs` | Property type | VERIFIED | `LogoData? ClientLogo { get; set; }` |
+
+### Plan 02 Key Links
+
+| From | To | Via | Status | Details |
+|------|----|-----|--------|---------|
+| `GraphUserDirectoryService.cs` | `GraphClientFactory` | Constructor injection | VERIFIED | `AppGraphClientFactory` alias resolves to `SharepointToolbox.Infrastructure.Auth.GraphClientFactory`; `CreateClientAsync` called |
+| `GraphUserDirectoryService.cs` | Microsoft.Graph PageIterator | SDK pagination | VERIFIED | `PageIterator<User, UserCollectionResponse>.CreatePageIterator(graphClient, response, callback)` + `IterateAsync` |
+
+### Plan 03 Key Links
+
+| From | To | Via | Status | Details |
+|------|----|-----|--------|---------|
+| `App.xaml.cs` | `BrandingRepository.cs` | AddSingleton registration | VERIFIED | `services.AddSingleton(_ => new BrandingRepository(Path.Combine(appData, "branding.json")))` at line 82 |
+| `App.xaml.cs` | `BrandingService.cs` | AddSingleton registration | VERIFIED | `services.AddSingleton<IBrandingService, BrandingService>()` at line 83 |
+| `App.xaml.cs` | `GraphUserDirectoryService.cs` | AddTransient registration | VERIFIED | `services.AddTransient<IGraphUserDirectoryService, GraphUserDirectoryService>()` at line 84 |
+
+---
+
+## Requirements Coverage
+
+| Requirement | Source Plan(s) | Description | Status | Evidence |
+|-------------|---------------|-------------|--------|----------|
+| BRAND-01 | 10-01, 10-03 | User can import an MSP logo in application settings (global, persisted across sessions) | SATISFIED | `BrandingService.ImportLogoAsync` + `SaveMspLogoAsync` + `BrandingRepository` persistence to `branding.json`; DI registered as Singleton |
+| BRAND-03 | 10-01, 10-03 | User can import a client logo per tenant profile | SATISFIED | `TenantProfile.ClientLogo` property added; `ImportLogoAsync` is format-agnostic (returns `LogoData` for caller to store); ViewModel in Phase 11 will wire the per-tenant save path |
+| BRAND-06 | 10-01, 10-02, 10-03 | Logo import validates format (PNG/JPG) and enforces 512 KB size limit | SATISFIED | Magic byte validation (PNG: 4 bytes, JPEG: 3 bytes) rejects all other formats; files over 512 KB compressed via two-pass WPF imaging; 5 validation/compression tests pass |
+
+**Orphaned requirements check:** REQUIREMENTS.md maps BRAND-01, BRAND-03, BRAND-06 exclusively to Phase 10. No additional Phase 10 requirements found in REQUIREMENTS.md outside these three. No orphaned requirements.
+
+---
+
+## Anti-Patterns Found
+
+| File | Line | Pattern | Severity | Impact |
+|------|------|---------|----------|--------|
+| `GraphUserDirectoryService.cs` | 32 | `// Pending real-tenant verification` comment | Info | Comment only; code is fully implemented. Filter `"accountEnabled eq true and userType eq 'Member'"` is implemented and correct. Verification against a live tenant is deferred to integration phase. |
+
+No blockers. No stubs. No empty implementations. No unimplemented TODO/FIXME items.
+
+---
+
+## Human Verification Required
+
+None. All goal behaviors are verifiable from source code and passing test output.
+
+The following items are acknowledged as integration-scope (not blocking):
+
+1. **Real-tenant filter verification** — The Graph API filter `accountEnabled eq true and userType eq 'Member'` cannot be verified without a live tenant. Noted in code comment and STATE.md. The logic is structurally correct per Graph SDK documentation.
+
+2. **WPF compression at test time** — `ImportLogoAsync_FileOver512KB_ReturnsCompressedUnder512KB` generates a large PNG using `System.Drawing.Bitmap` (available via `UseWPF=true` on net10.0-windows) and then compresses via WPF imaging APIs inside `BrandingService`. This test passes locally (confirmed: 14/14 branding tests pass). This test may behave differently in headless CI environments without a display — not a concern for this WPF desktop application.
+
+---
+
+## Gaps Summary
+
+No gaps. All 8 observable truths are verified. All artifacts exist, are substantive, and are correctly wired. All three required DI registrations are present in App.xaml.cs. The full test suite passes: 224 tests passed, 26 skipped (all skips are pre-existing integration tests requiring a live Graph/SharePoint endpoint), 0 failed.
+
+---
+
+## Test Results Summary
+
+| Test Suite | Passed | Skipped | Failed |
+|------------|--------|---------|--------|
+| BrandingRepositoryTests | 5 | 0 | 0 |
+| BrandingServiceTests | 9 | 0 | 0 |
+| GraphUserDirectoryServiceTests | 5 | 4 | 0 |
+| Full suite (all phases) | 224 | 26 | 0 |
+
+Commits verified: `2280f12`, `1303866`, `5e56a96`, `3ba5746`, `7e8e228` — all present in git history.
+
+---
+
+_Verified: 2026-04-08T12:00:00Z_
+_Verifier: Claude (gsd-verifier)_
@@ -0,0 +1,10 @@
+# Deferred Items — Phase 10 Branding Data Foundation
+
+## Pre-existing: BrandingServiceTests.cs blocks test project build
+
+**Found during:** Plan 10-02 Task 2 (test verification)
+**File:** `SharepointToolbox.Tests/Services/BrandingServiceTests.cs`
+**Issue:** File exists on disk (untracked in git) but references types (`BrandingService`, `BrandingRepository`, `LogoData`) that don't exist yet — these are the artifacts of plan 10-01. This blocked the test project from compiling, preventing `dotnet test` from running.
+**Impact:** Could not run GraphUserDirectoryServiceTests via `dotnet test` — only main project build verified.
+**Resolution:** Will be resolved when plan 10-01 is executed and BrandingService types are created.
+**Action needed:** Execute plan 10-01 before or alongside 10-02 to restore test compilation.
@@ -1,581 +1,443 @@
-# Architecture Research
+# Architecture Patterns

-**Domain:** C#/WPF SharePoint Online Administration Desktop Tool
-**Researched:** 2026-04-02
-**Confidence:** HIGH
-
-## Standard Architecture
-
-### System Overview
-
-```
-┌─────────────────────────────────────────────────────────────────────┐
-│                         PRESENTATION LAYER                           │
-│  ┌──────────────┐  ┌─────────────────────────────────────────────┐  │
-│  │   MainWindow │  │             Feature Views (XAML)             │  │
-│  │   Shell.xaml │  │  Permissions │ Storage │ Search │ Templates  │  │
-│  │              │  │  Duplicates  │ Bulk    │ Reports │ Settings  │  │
-│  └──────┬───────┘  └──────────────────────┬────────────────────┘  │
-│         │ DataContext binding              │ DataContext binding     │
-├─────────┴─────────────────────────────────┴────────────────────────┤
-│                          VIEWMODEL LAYER                             │
-│  ┌─────────────┐  ┌──────────────────────────────────────────────┐  │
-│  │  MainWindow │  │           Feature ViewModels                  │  │
-│  │  ViewModel  │  │  PermissionsVM │ StorageVM │ SearchVM         │  │
-│  │  (nav/shell)│  │  TemplatesVM   │ BulkOpsVM │ DuplicatesVM     │  │
-│  └──────┬──────┘  └───────────────────────┬──────────────────────┘  │
-│         │ ICommand, ObservableProperty     │ AsyncRelayCommand        │
-├─────────┴─────────────────────────────────┴────────────────────────┤
-│                           SERVICE LAYER                              │
-│  ┌────────────────┐  ┌─────────────────┐  ┌──────────────────────┐  │
-│  │ AuthService    │  │ SharePoint       │  │ Cross-Cutting        │  │
-│  │ SessionManager │  │ Feature Services │  │ Services             │  │
-│  │ TenantSession  │  │ PermissionsService│ │ ReportExportService  │  │
-│  │                │  │ StorageService   │  │ LocalizationService  │  │
-│  │                │  │ SearchService    │  │ DialogService        │  │
-│  │                │  │ TemplateService  │  │ SettingsService      │  │
-│  └────────┬───────┘  └────────┬────────┘  └──────────────────────┘  │
-│           │ ClientContext      │ IProgress<T>, CancellationToken      │
-├───────────┴────────────────────┴────────────────────────────────────┤
-│                    INFRASTRUCTURE / INTEGRATION LAYER                │
-│  ┌──────────────────┐  ┌───────────────────┐  ┌──────────────────┐  │
-│  │  PnP Framework   │  │ Microsoft Graph    │  │  Local Storage   │  │
-│  │  AuthManager     │  │ GraphServiceClient │  │  JSON Files      │  │
-│  │  ClientContext   │  │ (Graph operations) │  │  Profiles        │  │
-│  │  (CSOM ops)      │  │                   │  │  Templates       │  │
-│  └──────────────────┘  └───────────────────┘  └──────────────────┘  │
-└─────────────────────────────────────────────────────────────────────┘
-```
-
-### Component Responsibilities
-
-| Component | Responsibility | Typical Implementation |
-|-----------|----------------|------------------------|
-| MainWindow Shell | Tab navigation, tenant selector, app chrome, log panel | XAML with TabControl or navigation frame |
-| Feature Views | User input forms, result grids, progress indicators | UserControl XAML, zero code-behind |
-| Feature ViewModels | Commands, observable state, orchestrates services | ObservableObject subclass, AsyncRelayCommand |
-| AuthService / SessionManager | Multi-tenant session lifecycle, token cache, active tenant state | Singleton, MSAL token cache per tenant |
-| TenantSession | Per-tenant PnP ClientContext + auth token | Immutable record, created by AuthService |
-| SharePoint Feature Services | Domain logic that calls PnP Framework or Graph | Stateless class, injectable, cancellable |
-| ReportExportService | HTML/CSV generation from result models | Stateless, template-based string builder |
-| LocalizationService | Key-based EN/FR translation, dynamic language switch | Singleton, loads lang/*.json, INotifyPropertyChanged |
-| SettingsService | Read/write JSON settings, profiles, templates | Singleton, file I/O wrapped in async |
-| DialogService | Open files, show message boxes, pick folders | Interface + WPF implementation, testable |
+**Domain:** C#/WPF MVVM desktop app — SharePoint Online MSP admin tool
+**Feature scope:** Report branding (MSP/client logos in HTML) + User directory browse mode
+**Researched:** 2026-04-08
+**Confidence:** HIGH — based on direct codebase inspection, not assumptions

 ---

-## Recommended Project Structure
+## Existing Architecture (Baseline)

 ```
-SharepointToolbox/
-├── App.xaml                        # Application entry, DI container bootstrap
-├── App.xaml.cs                     # Host builder, service registration
-│
-├── Core/                           # Domain models — no WPF dependencies
-│   ├── Models/
-│   │   ├── PermissionEntry.cs
-│   │   ├── StorageMetrics.cs
-│   │   ├── SiteTemplate.cs
-│   │   ├── TenantProfile.cs
-│   │   └── SearchResult.cs
-│   ├── Interfaces/
-│   │   ├── IAuthService.cs
-│   │   ├── IPermissionsService.cs
-│   │   ├── IStorageService.cs
-│   │   ├── ISearchService.cs
-│   │   ├── ITemplateService.cs
-│   │   ├── IBulkOpsService.cs
-│   │   ├── IDuplicateService.cs
-│   │   ├── IReportExportService.cs
-│   │   ├── ISettingsService.cs
-│   │   ├── ILocalizationService.cs
-│   │   └── IDialogService.cs
-│   └── Exceptions/
-│       ├── SharePointConnectionException.cs
-│       └── AuthenticationException.cs
-│
-├── Services/                       # Business logic + infrastructure
-│   ├── Auth/
-│   │   ├── AuthService.cs          # PnP AuthenticationManager wrapper
-│   │   ├── SessionManager.cs       # Multi-tenant session store
-│   │   └── TenantSession.cs        # Per-tenant PnP ClientContext holder
-│   ├── SharePoint/
-│   │   ├── PermissionsService.cs   # Recursive permission scanning
-│   │   ├── StorageService.cs       # Storage metric traversal
-│   │   ├── SearchService.cs        # KQL-based search via PnP/Graph
-│   │   ├── TemplateService.cs      # Capture & apply site templates
-│   │   ├── DuplicateService.cs     # File/folder duplicate detection
-│   │   └── BulkOpsService.cs       # Transfer, site creation, member add
-│   ├── Reporting/
-│   │   ├── HtmlReportService.cs    # Self-contained HTML + JS reports
-│   │   └── CsvExportService.cs     # CSV export
-│   ├── LocalizationService.cs      # EN/FR key-value translations
-│   ├── SettingsService.cs          # JSON profiles, templates, settings
-│   └── DialogService.cs            # WPF dialog abstractions
-│
-├── ViewModels/                     # WPF-aware but UI-framework-agnostic
-│   ├── MainWindowViewModel.cs      # Shell nav, tenant switcher, log
-│   ├── Permissions/
-│   │   └── PermissionsViewModel.cs
-│   ├── Storage/
-│   │   └── StorageViewModel.cs
-│   ├── Search/
-│   │   └── SearchViewModel.cs
-│   ├── Templates/
-│   │   └── TemplatesViewModel.cs
-│   ├── Duplicates/
-│   │   └── DuplicatesViewModel.cs
-│   ├── BulkOps/
-│   │   └── BulkOpsViewModel.cs
-│   └── Settings/
-│       └── SettingsViewModel.cs
-│
-├── Views/                          # XAML — no business logic
-│   ├── MainWindow.xaml
-│   ├── Permissions/
-│   │   └── PermissionsView.xaml
-│   ├── Storage/
-│   │   └── StorageView.xaml
-│   ├── Search/
-│   │   └── SearchView.xaml
-│   ├── Templates/
-│   │   └── TemplatesView.xaml
-│   ├── Duplicates/
-│   │   └── DuplicatesView.xaml
-│   ├── BulkOps/
-│   │   └── BulkOpsView.xaml
-│   └── Settings/
-│       └── SettingsView.xaml
-│
-├── Controls/                       # Reusable WPF controls
-│   ├── TenantSelectorControl.xaml
-│   ├── LogPanelControl.xaml
-│   ├── ProgressOverlayControl.xaml
-│   └── StorageChartControl.xaml    # LiveCharts2 wrapper
-│
-├── Converters/                     # IValueConverter implementations
-│   ├── BytesToStringConverter.cs
-│   ├── BoolToVisibilityConverter.cs
-│   └── PermissionColorConverter.cs
-│
-├── Resources/                      # Styles, brushes, theme
-│   ├── Styles.xaml
-│   └── Colors.xaml
-│
-├── Lang/                           # Language files
-│   ├── en.json
-│   └── fr.json
-│
-└── Infrastructure/
-    └── Behaviors/                  # XAML attached behaviors (no code-behind workaround)
-        └── ScrollToBottomBehavior.cs
+Core/
+  Models/         — TenantProfile, AppSettings, domain records (all POCOs/records)
+  Messages/       — WeakReferenceMessenger value message types
+  Helpers/        — Static utility classes
+
+Infrastructure/
+  Auth/           — MsalClientFactory, GraphClientFactory (MSAL PCA per-tenant + Graph SDK bridge)
+  Persistence/    — ProfileRepository, SettingsRepository, TemplateRepository (JSON, atomic write-then-replace)
+  Logging/        — LogPanelSink (Serilog sink to in-app RichTextBox)
+
+Services/
+  Export/         — Concrete HTML/CSV export services per domain (no interface, consumed directly)
+  *.cs            — Domain services with IXxx interfaces
+
+ViewModels/
+  FeatureViewModelBase.cs         — Abstract base: RunCommand, CancelCommand, ProgressValue, StatusMessage,
+                                    GlobalSites, WeakReferenceMessenger registration
+  MainWindowViewModel.cs          — Toolbar: tenant picker, Connect, global site picker, broadcasts TenantSwitchedMessage
+  Tabs/                           — One ViewModel per tab, all extend FeatureViewModelBase
+  ProfileManagementViewModel.cs   — Profile CRUD dialog VM
+
+Views/
+  Dialogs/   — ProfileManagementDialog, SitePickerDialog, ConfirmBulkOperationDialog, FolderBrowserDialog
+  Tabs/      — One UserControl per tab (XAML + code-behind)
+
+App.xaml.cs — Generic Host IServiceCollection DI registration for all layers
 ```

-### Structure Rationale
+### Key Patterns Already Established

- **Core/**: Pure C# — no WPF references. Interfaces here make services testable. Models are plain data classes.
- **Services/**: All domain logic and I/O. Injected via constructor DI. No static state.
- **ViewModels/**: Mirror the feature structure. Depend on service interfaces, never on concrete implementations.
- **Views/**: XAML-only. No logic. `DataContext` set by DI or ViewModelLocator pattern at startup.
- **Controls/**: Reusable UI widgets that encapsulate chart, log, and progress concerns.
+| Pattern | How It Works |
+|---------|-------------|
+| Tenant switching | `MainWindowViewModel.OnSelectedProfileChanged` broadcasts `TenantSwitchedMessage` via `WeakReferenceMessenger`; each tab VM overrides `OnTenantSwitched(profile)` |
+| Global site propagation | `GlobalSitesChangedMessage` received in `FeatureViewModelBase.OnGlobalSitesReceived` |
+| HTML export | Concrete service class (e.g. `UserAccessHtmlExportService`), `BuildHtml(entries)` returns a string, `WriteAsync(entries, path, ct)` writes it. No interface. Pure data-in, HTML-out. |
+| JSON persistence | Repository pattern: constructor takes `string filePath`, atomic write via `.tmp` + round-trip JSON validation before `File.Move`, `SemaphoreSlim` write lock. |
+| DI registration | All in `App.xaml.cs RegisterServices()`. Export services and ViewModels are `AddTransient`; shared infrastructure is `AddSingleton`. |
+| Dialog factory | View code-behind sets `ViewModel.OpenXxxDialog = () => new XxxDialog(...)` — keeps dialogs out of ViewModel layer |
+| People-picker search | `IGraphUserSearchService.SearchUsersAsync(clientId, query, maxResults, ct)` calls Graph `/users?$filter=startsWith(...)` with `ConsistencyLevel: eventual` |
+| Test constructor | `UserAccessAuditViewModel` has a `internal` 3-param constructor without export services — test pattern to replicate for new injections |

 ---

-## Architectural Patterns
+## Feature 1: Report Branding (MSP/Client Logos in HTML Reports)

-### Pattern 1: ObservableObject + AsyncRelayCommand (CommunityToolkit.Mvvm)
+### What It Needs

-**What:** Use `ObservableObject` as base class for all ViewModels. Use `[ObservableProperty]` source-gen attribute for bindable properties. Use `AsyncRelayCommand` (with `CancellationToken`) for all SharePoint operations.
+- **MSP logo** — one global image, shown in every HTML report from every tenant
+- **Client logo** — one image per tenant, shown in reports for that tenant only
+- **Storage** — base64-encoded strings in JSON (no separate image files — preserves atomic save semantics and single-data-folder design)
+- **Embedding** — `data:image/...;base64,...` `<img>` tag injected into the HTML header (maintains self-contained HTML invariant — zero external file references)
+- **User action** — file picker → read bytes → detect MIME type → convert to base64 → store in JSON → preview in UI

-**When to use:** All ViewModels. This is the standard pattern for .NET 8 + WPF.
+### New Components (create from scratch)

-**Trade-offs:** Source generators require C# 10+. Generated partial class syntax is unfamiliar at first but eliminates 80% of boilerplate.
-
-**Example:**
+**`Core/Models/BrandingSettings.cs`**
 ```csharp
-public partial class PermissionsViewModel : ObservableObject
+public class BrandingSettings
 {
-    private readonly IPermissionsService _permissionsService;
-
-    [ObservableProperty]
-    private bool _isRunning;
-
-    [ObservableProperty]
-    private string _statusMessage = string.Empty;
-
-    [ObservableProperty]
-    private ObservableCollection<PermissionEntry> _results = new();
-
-    public IAsyncRelayCommand RunReportCommand { get; }
-
-    public PermissionsViewModel(IPermissionsService permissionsService)
-    {
-        _permissionsService = permissionsService;
-        RunReportCommand = new AsyncRelayCommand(RunReportAsync, allowConcurrentExecutions: false);
-    }
-
-    private async Task RunReportAsync(CancellationToken cancellationToken)
-    {
-        IsRunning = true;
-        StatusMessage = "Scanning permissions...";
-        try
-        {
-            var results = await _permissionsService.ScanAsync(
-                SiteUrl, cancellationToken,
-                new Progress<string>(msg => StatusMessage = msg));
-            Results = new ObservableCollection<PermissionEntry>(results);
-        }
-        finally { IsRunning = false; }
-    }
+    public string? MspLogoBase64 { get; set; }
+    public string? MspLogoMimeType { get; set; }  // "image/png", "image/jpeg", etc.
 }
 ```
+Belongs in Core/Models alongside AppSettings. Kept separate — branding may grow independently of general app settings.

-### Pattern 2: Multi-Tenant Session Manager
-
-**What:** A singleton `SessionManager` holds a dictionary of `TenantSession` objects keyed by tenant URL. When the user selects a tenant profile, the session is reused if still valid (MSAL token cache handles token refresh). No re-authentication unless the token is expired and silent refresh fails.
-
-**When to use:** Every SharePoint service operation resolves `IAuthService.GetSessionAsync(tenantUrl)` before calling PnP Framework.
-
-**Trade-offs:** MSAL token cache must be persisted across app restarts for seamless reconnect. For interactive login, MSAL `PublicClientApplicationBuilder` with `WithParentActivityOrWindow` is required on Windows to avoid a blank browser window.
-
-**Example:**
+**`Core/Models/ReportBranding.cs`**
 ```csharp
-public class SessionManager
-{
-    private readonly ConcurrentDictionary<string, TenantSession> _sessions = new();
-
-    public async Task<TenantSession> GetOrCreateSessionAsync(
-        TenantProfile profile, CancellationToken ct)
-    {
-        if (_sessions.TryGetValue(profile.TenantUrl, out var session)
-            && !session.IsExpired)
-            return session;
-
-        var authManager = new PnP.Framework.AuthenticationManager(
-            profile.ClientId,
-            openBrowserCallback: url => Process.Start(new ProcessStartInfo(url) { UseShellExecute = true }));
-
-        var ctx = await authManager.GetContextAsync(profile.TenantUrl);
-        var newSession = new TenantSession(profile, ctx, authManager);
-        _sessions[profile.TenantUrl] = newSession;
-        return newSession;
-    }
-}
+public record ReportBranding(
+    string? MspLogoBase64,
+    string? MspLogoMimeType,
+    string? ClientLogoBase64,
+    string? ClientLogoMimeType);
 ```
+Lightweight data transfer record assembled at export time from BrandingSettings + current TenantProfile. Not persisted directly — constructed on demand.

-### Pattern 3: IProgress\<T\> + CancellationToken for All Long Operations
+**`Infrastructure/Persistence/BrandingRepository.cs`**
+Same pattern as `SettingsRepository`: constructor takes `string filePath`, atomic write-then-replace, `SemaphoreSlim` write lock. File: `%AppData%\SharepointToolbox\branding.json`.

-**What:** Every service method that calls SharePoint accepts `IProgress<OperationProgress>` and `CancellationToken`. The ViewModel creates `Progress<T>` (which marshals callbacks to the UI thread automatically) and `CancellationTokenSource`.
-
-**When to use:** All SharePoint service methods. This replaces the PowerShell runspace + timer polling pattern from the existing app.
-
-**Trade-offs:** `Progress<T>` captures SynchronizationContext on creation — must be created on the UI thread (i.e., inside the ViewModel, not inside the service).
-
-**Example:**
+**`Services/BrandingService.cs`**
 ```csharp
-// In ViewModel (UI thread context):
-var cts = new CancellationTokenSource();
-CancelCommand = new RelayCommand(() => cts.Cancel());
-var progress = new Progress<OperationProgress>(p => StatusMessage = p.Message);
-
-// In Service (any thread):
-public async Task<IList<PermissionEntry>> ScanAsync(
-    string siteUrl,
-    CancellationToken ct,
-    IProgress<OperationProgress> progress)
+public class BrandingService
 {
-    progress.Report(new OperationProgress("Connecting..."));
-    using var ctx = await _sessionManager.GetOrCreateSessionAsync(..., ct);
-    // ... recursive scanning ...
-    ct.ThrowIfCancellationRequested();
-    progress.Report(new OperationProgress($"Found {results.Count} entries"));
-    return results;
+    public Task<BrandingSettings> GetBrandingAsync();
+    public Task SetMspLogoAsync(string filePath);     // reads file, detects MIME, converts to base64, saves
+    public Task ClearMspLogoAsync();
 }
 ```
+Thin orchestration, same pattern as `SettingsService`. MSP logo only — client logo is managed via `ProfileService` (it belongs to `TenantProfile`).

-### Pattern 4: Messenger for Cross-ViewModel Events
+### Modified Components

-**What:** Use `CommunityToolkit.Mvvm.Messaging.WeakReferenceMessenger` for decoupled communication between ViewModels (e.g., "tenant switched" notifies all feature VMs to reset state, "log entry added" updates the log panel ViewModel).
-
-**When to use:** When two ViewModels need to communicate without direct reference (shell ↔ feature VMs, service callbacks ↔ log panel).
-
-**Trade-offs:** Weak references mean recipients must be alive (held by DI container). Don't use for per-request data passing — use method return values for that.
-
-### Pattern 5: Dependency Injection via Microsoft.Extensions.Hosting
-
-**What:** Bootstrap the app with `Host.CreateDefaultBuilder()` in `App.xaml.cs`. Register all services, ViewModels, and the main window in the DI container. Use constructor injection everywhere — no service locator anti-pattern.
-
-**Example:**
+**`Core/Models/TenantProfile.cs`** — Add two nullable string properties:
 ```csharp
-// App.xaml.cs
-protected override void OnStartup(StartupEventArgs e)
+public string? ClientLogoBase64 { get; set; }
+public string? ClientLogoMimeType { get; set; }
+```
+This is backward-compatible. `ProfileRepository` uses `JsonSerializer` with `PropertyNameCaseInsensitive: true` — missing JSON fields deserialize to null without error. Existing `profiles.json` files continue to load correctly.
+
+**All HTML export services** — Add `ReportBranding? branding = null` optional parameter to every `BuildHtml()` overload. When non-null and at least one logo is present, inject a branding header div between `<body>` open and `<h1>`:
+
+```html
+<div class="brand-header" style="display:flex;align-items:center;gap:16px;padding:16px 24px 0;">
+  <!-- only rendered if logo present -->
+  <img src="data:{mimeType};base64,{base64}" style="max-height:60px;max-width:200px;" alt="MSP" />
+  <img src="data:{mimeType};base64,{base64}" style="max-height:60px;max-width:200px;" alt="Client" />
+</div>
+```
+
+When `branding` is null (existing callers) the block is omitted entirely. No behavior change for callers that do not pass branding.
+
+Affected services (all in `Services/Export/`):
+- `HtmlExportService` (two `BuildHtml` overloads — `PermissionEntry` and `SimplifiedPermissionEntry`)
+- `UserAccessHtmlExportService`
+- `StorageHtmlExportService` (two `BuildHtml` overloads — with and without `FileTypeMetric`)
+- `SearchHtmlExportService`
+- `DuplicatesHtmlExportService`
+
+**ViewModels that call HTML export** — All `ExportHtmlAsync` methods need to resolve branding before calling the export service. The ViewModel calls `BrandingService.GetBrandingAsync()` and reads `_currentProfile.ClientLogoBase64` to assemble a `ReportBranding`, then passes it to `BuildHtml`.
+
+Affected ViewModels: `PermissionsViewModel`, `UserAccessAuditViewModel`, `StorageViewModel`, `SearchViewModel`, `DuplicatesViewModel`. Each gets `BrandingService` injected via constructor.
+
+**`ViewModels/Tabs/SettingsViewModel.cs`** — Add MSP logo management:
+```csharp
+[ObservableProperty] private string? _mspLogoPreviewBase64;
+public RelayCommand BrowseMspLogoCommand { get; }
+public RelayCommand ClearMspLogoCommand { get; }
+```
+On browse: open `OpenFileDialog` (filter: PNG, JPG, GIF) → call `BrandingService.SetMspLogoAsync(path)` → reload and refresh `MspLogoPreviewBase64`.
+
+**`Views/Tabs/SettingsView.xaml`** — Add a "Report Branding — MSP Logo" section:
+- `<Image>` bound to `MspLogoPreviewBase64` via a base64-to-BitmapSource converter
+- "Browse Logo" button → `BrowseMspLogoCommand`
+- "Clear" button → `ClearMspLogoCommand`
+- Note label: "Applies to all reports"
+
+**Client logo placement:** Client logo belongs to a `TenantProfile`, not to global settings. The natural place to manage it is `ProfileManagementDialog` (already handles profile CRUD). Add logo fields there rather than in SettingsView.
+
+**`ViewModels/ProfileManagementViewModel.cs`** — Add client logo management per profile:
+```csharp
+[ObservableProperty] private string? _clientLogoPreviewBase64;
+public RelayCommand BrowseClientLogoCommand { get; }
+public RelayCommand ClearClientLogoCommand { get; }
+```
+On browse: read image bytes → base64 → set on the being-edited `TenantProfile` object before saving. Uses `ProfileService.AddProfileAsync` / rename pipeline that already exists.
+
+**`Views/Dialogs/ProfileManagementDialog.xaml`** — Add client logo fields to the add/edit profile form (same pattern as SettingsView branding section).
+
+### Data Flow: Report Branding
+
+```
+User picks MSP logo (SettingsView "Browse Logo" button)
+  → SettingsViewModel.BrowseMspLogoCommand
+    → OpenFileDialog in View code-behind or VM (follow existing BrowseFolder pattern)
+    → BrandingService.SetMspLogoAsync(path)
+      → File.ReadAllBytesAsync → Convert.ToBase64String
+      → detect MIME from extension (.png → image/png, .jpg/.jpeg → image/jpeg, .gif → image/gif)
+      → BrandingRepository.SaveAsync(BrandingSettings)
+    → ViewModel refreshes MspLogoPreviewBase64
+
+User runs export (e.g. ExportHtmlCommand in UserAccessAuditViewModel)
+  → BrandingService.GetBrandingAsync() → BrandingSettings
+  → reads _currentProfile.ClientLogoBase64, _currentProfile.ClientLogoMimeType
+  → new ReportBranding(mspBase64, mspMime, clientBase64, clientMime)
+  → UserAccessHtmlExportService.BuildHtml(entries, branding)
+    → injects <img> data URIs in header when base64 is non-null
+  → writes HTML file
+```
+
+---
+
+## Feature 2: User Directory Browse Mode
+
+### What It Needs
+
+The existing `UserAccessAuditView` has a people-picker: search box → Graph API `startsWith` filter → autocomplete dropdown → add to `SelectedUsers`. Directory browse mode is an alternative to the search box: show a paginated, filterable list of all tenant users, allow multi-select, bulk-add to `SelectedUsers`.
+
+This is purely additive. The underlying audit logic (`IUserAccessAuditService`, `RunOperationAsync`, `SelectedUsers` collection, export commands) is completely unchanged.
+
+### New Components (create from scratch)
+
+**`Core/Models/PagedUserResult.cs`**
+```csharp
+public record PagedUserResult(
+    IReadOnlyList<GraphUserResult> Users,
+    string? NextPageToken);  // null = last page
+```
+
+**`Services/IGraphUserDirectoryService.cs`**
+```csharp
+public interface IGraphUserDirectoryService
 {
-    _host = Host.CreateDefaultBuilder()
-        .ConfigureServices(services =>
-        {
-            // Core services (singletons)
-            services.AddSingleton<ISettingsService, SettingsService>();
-            services.AddSingleton<ILocalizationService, LocalizationService>();
-            services.AddSingleton<SessionManager>();
-            services.AddSingleton<IAuthService, AuthService>();
-            services.AddSingleton<IDialogService, DialogService>();
-
-            // Feature services (transient — no shared state)
-            services.AddTransient<IPermissionsService, PermissionsService>();
-            services.AddTransient<IStorageService, StorageService>();
-            services.AddTransient<ISearchService, SearchService>();
-
-            // ViewModels
-            services.AddTransient<MainWindowViewModel>();
-            services.AddTransient<PermissionsViewModel>();
-            services.AddTransient<StorageViewModel>();
-
-            // Views
-            services.AddSingleton<MainWindow>();
-        })
-        .Build();
-
-    _host.Start();
-    var mainWindow = _host.Services.GetRequiredService<MainWindow>();
-    mainWindow.DataContext = _host.Services.GetRequiredService<MainWindowViewModel>();
-    mainWindow.Show();
+    Task<PagedUserResult> GetUsersPageAsync(
+        string clientId,
+        string? filter = null,
+        string? pageToken = null,
+        int pageSize = 100,
+        CancellationToken ct = default);
 }
 ```

---
+**`Services/GraphUserDirectoryService.cs`**
+Reuses `GraphClientFactory` (already injected elsewhere). Calls `graphClient.Users.GetAsync()` without the `startsWith` constraint used in search — uses `$top=100` with cursor-based paging via Graph's `@odata.nextLink`. Returns `PagedUserResult` so callers control pagination. Uses `ConsistencyLevel: eventual` + `$count=true` (same as existing search service).

-## Data Flow
+### Modified Components

-### SharePoint Operation Request Flow
+**`ViewModels/Tabs/UserAccessAuditViewModel.cs`** — Add browse mode state:

-```
-User clicks "Run" button
-        ↓
-View command binding triggers AsyncRelayCommand.ExecuteAsync()
-        ↓
-ViewModel validates inputs → creates CancellationTokenSource + Progress<T>
-        ↓
-ViewModel calls IFeatureService.ScanAsync(params, ct, progress)
-        ↓
-Service calls SessionManager.GetOrCreateSessionAsync(profile, ct)
-        ↓
-SessionManager checks cache → reuses token or triggers interactive login
-        ↓
-Service executes PnP Framework / Graph SDK calls (async, awaited)
-        ↓
-Service reports incremental progress → Progress<T>.Report() → UI thread
-        ↓
-Service returns result collection to ViewModel
-        ↓
-ViewModel updates ObservableCollection → WPF binding refreshes DataGrid
-        ↓
-ViewModel sets IsRunning = false → progress overlay hides
+```csharp
+[ObservableProperty] private bool _isBrowseModeActive;
+[ObservableProperty] private ObservableCollection<GraphUserResult> _directoryUsers = new();
+[ObservableProperty] private string _directoryFilter = string.Empty;
+[ObservableProperty] private bool _isLoadingDirectory;
+[ObservableProperty] private bool _hasMoreDirectoryPages;
+
+private string? _directoryNextPageToken;
+
+public IAsyncRelayCommand LoadDirectoryCommand { get; }
+public IAsyncRelayCommand LoadMoreDirectoryCommand { get; }
+public RelayCommand<IList<GraphUserResult>> AddDirectoryUsersCommand { get; }
 ```

-### Authentication & Session Flow
+`partial void OnIsBrowseModeActiveChanged(bool value)` → when `value == true`, fire `LoadDirectoryCommand` to populate page 1.
+
+`partial void OnDirectoryFilterChanged(string value)` → debounce 300ms (same pattern as `OnSearchQueryChanged`), re-fire `LoadDirectoryCommand` with new filter, clear `_directoryNextPageToken`.
+
+The `IGraphUserDirectoryService` is added to the constructor. The internal test constructor (currently 3 params) gets a 4-param overload adding the directory service with a null-safe default, or a new explicit test constructor.
+
+**`App.xaml.cs RegisterServices()`** — Add:
+```csharp
+services.AddTransient<IGraphUserDirectoryService, GraphUserDirectoryService>();
+```
+The `UserAccessAuditViewModel` transient registration picks up the new injection automatically (DI resolves by type).
+
+**`UserAccessAuditViewModel.OnTenantSwitched`** — Also clear `DirectoryUsers`, reset `_directoryNextPageToken`, `HasMoreDirectoryPages`, `IsLoadingDirectory`.
+
+**`Views/Tabs/UserAccessAuditView.xaml`** — Add to the top of the left panel:
+- Mode toggle: two `RadioButton`s or `ToggleButton`s bound to `IsBrowseModeActive`
+- "Search" panel: existing `GroupBox` shown when `IsBrowseModeActive == false`
+- "Browse" panel: new `GroupBox` shown when `IsBrowseModeActive == true`, containing:
+  - Filter `TextBox` bound to `DirectoryFilter`
+  - `ListView` with `SelectionMode="Extended"` bound to `DirectoryUsers`, `SelectionChanged` handler in code-behind
+  - "Add Selected" `Button` → `AddDirectoryUsersCommand`
+  - "Load more" `Button` shown when `HasMoreDirectoryPages == true` → `LoadMoreDirectoryCommand`
+  - Loading indicator (existing `IsSearching` pattern, but for `IsLoadingDirectory`)
+- Show/hide panels via `DataTrigger` on `IsBrowseModeActive`
+
+**`Views/Tabs/UserAccessAuditView.xaml.cs`** — Add `SelectionChanged` handler to pass `ListView.SelectedItems` (as `IList<GraphUserResult>`) to `AddDirectoryUsersCommand`. Follow the existing `SearchResultsListBox_SelectionChanged` pattern.
+
+### Data Flow: Directory Browse Mode

 ```
-User selects tenant profile from dropdown
-        ↓
-MainWindowViewModel calls SessionManager.SetActiveProfile(profile)
-        ↓
-SessionManager publishes TenantChangedMessage via WeakReferenceMessenger
-        ↓
-All feature ViewModels receive message → reset their state/results
-        ↓
-On first operation: SessionManager.GetOrCreateSessionAsync()
-        ↓
-   [Cache hit: token valid] → return existing ClientContext immediately
-   [Cache miss / expired]   → PnP AuthManager.GetContextAsync()
-                                    ↓
-                               MSAL silent token refresh attempt
-                                    ↓
-                          [Silent fails] → open browser for interactive login
-                                    ↓
-                          User authenticates → token cached by MSAL
-                                    ↓
-                          ClientContext returned to caller
-```
+User clicks "Browse" mode toggle
+  → IsBrowseModeActive = true
+  → OnIsBrowseModeActiveChanged fires LoadDirectoryCommand
+  → GraphUserDirectoryService.GetUsersPageAsync(clientId, filter: null, pageToken: null, 100, ct)
+    → Graph GET /users?$select=displayName,userPrincipalName,mail&$top=100&$orderby=displayName
+    → returns PagedUserResult { Users = [...100 items], NextPageToken = "..." }
+  → DirectoryUsers = new collection of returned users
+  → HasMoreDirectoryPages = (NextPageToken != null)
+  → _directoryNextPageToken = returned token

-### Report Export Flow
+User types in DirectoryFilter
+  → debounce 300ms
+  → LoadDirectoryCommand re-fires with filter
+  → DirectoryUsers replaced with filtered page 1

-```
-Service returns List<TModel> to ViewModel
-        ↓
-User clicks "Export CSV" or "Export HTML"
-        ↓
-ViewModel calls IReportExportService.ExportAsync(results, format, outputPath)
-        ↓
-ReportExportService generates file (string building, no blocking I/O on UI thread)
-        ↓
-ViewModel calls IDialogService.OpenFile(outputPath) to auto-open result
-```
+User selects users in ListView + clicks "Add Selected"
+  → AddDirectoryUsersCommand(selectedItems)
+  → for each: if not already in SelectedUsers by UPN → SelectedUsers.Add(user)

-### State Management
-
-```
-AppState (DI-managed singletons):
-  SessionManager     → active profile, tenant sessions dict
-  SettingsService    → user prefs, data folder, profiles list
-  LocalizationService → current language, translation dict
-
-Per-Operation State (ViewModel-local):
-  ObservableCollection<T>  → bound to DataGrid
-  CancellationTokenSource  → cancel button binding
-  IsRunning (bool)         → progress overlay binding
-  StatusMessage (string)   → progress label binding
+User clicks "Load more"
+  → LoadMoreDirectoryCommand
+  → GetUsersPageAsync(clientId, currentFilter, _directoryNextPageToken, 100, ct)
+  → DirectoryUsers items appended (not replaced)
+  → _directoryNextPageToken updated
 ```

 ---

-## Component Boundaries
+## Component Boundary Summary

-### What Communicates With What
+### New Components (create)

-| Boundary | Communication Method | Direction | Notes |
-|----------|---------------------|-----------|-------|
-| View ↔ ViewModel | WPF data binding (two-way for inputs, one-way for results) | Both | No code-behind |
-| ViewModel ↔ Service | Constructor-injected interface, async method call | VM → Service | Services return Task\<T\> |
-| ViewModel ↔ ViewModel | WeakReferenceMessenger messages | Broadcast | Tenant switch, log events |
-| Service ↔ SessionManager | `GetOrCreateSessionAsync()` | Service → SessionMgr | Every SharePoint call |
-| SessionManager ↔ PnP Framework | `AuthenticationManager.GetContextAsync()` | SessionMgr → PnP | On cache miss only |
-| Service ↔ Graph SDK | `GraphServiceClient` method calls | Service → Graph | For Graph-only operations |
-| SettingsService ↔ FileSystem | `System.Text.Json` + `File.ReadAllText/WriteAllText` | Both | Async I/O |
-| LocalizationService ↔ Views | XAML binding to translated string properties | Service → View | Via singleton binding |
+| Component | Layer | Type | Purpose |
+|-----------|-------|------|---------|
+| `BrandingSettings` | Core/Models | class | MSP logo storage (base64 + MIME type) |
+| `ReportBranding` | Core/Models | record | Data passed to `BuildHtml` overloads at export time |
+| `BrandingRepository` | Infrastructure/Persistence | class | JSON load/save for `BrandingSettings` |
+| `BrandingService` | Services | class | Orchestrates logo file read / MIME detect / base64 convert / save |
+| `PagedUserResult` | Core/Models | record | Page of `GraphUserResult` items + next-page token |
+| `IGraphUserDirectoryService` | Services | interface | Contract for paginated tenant user enumeration |
+| `GraphUserDirectoryService` | Services | class | Graph API user listing with cursor pagination |

-### What Must NOT Cross Boundaries
+Total new files: 7

- Views must not call services directly — all via ViewModel commands
- Services must not reference any WPF types (`System.Windows.*`) — use `IProgress<T>` for UI feedback
- ViewModels must not instantiate `ClientContext` or `AuthenticationManager` directly — only via `IAuthService`
- SessionManager is the only class that holds `ClientContext` objects — services receive them per-operation
+### Modified Components (extend)
+
+| Component | Change | Risk |
+|-----------|--------|------|
+| `TenantProfile` | + 2 nullable logo props | LOW — JSON backward-compatible |
+| `HtmlExportService` | + optional `ReportBranding?` on 2 overloads | LOW — optional param, existing callers unaffected |
+| `UserAccessHtmlExportService` | + optional `ReportBranding?` | LOW |
+| `StorageHtmlExportService` | + optional `ReportBranding?` on 2 overloads | LOW |
+| `SearchHtmlExportService` | + optional `ReportBranding?` | LOW |
+| `DuplicatesHtmlExportService` | + optional `ReportBranding?` | LOW |
+| `PermissionsViewModel` | + inject `BrandingService`, use in ExportHtmlAsync | LOW |
+| `UserAccessAuditViewModel` | + inject `BrandingService` + `IGraphUserDirectoryService`, browse mode state/commands | MEDIUM |
+| `StorageViewModel` | + inject `BrandingService`, use in ExportHtmlAsync | LOW |
+| `SearchViewModel` | + inject `BrandingService`, use in ExportHtmlAsync | LOW |
+| `DuplicatesViewModel` | + inject `BrandingService`, use in ExportHtmlAsync | LOW |
+| `SettingsViewModel` | + inject `BrandingService`, MSP logo commands + preview property | LOW |
+| `ProfileManagementViewModel` | + client logo browse/preview/clear | LOW |
+| `SettingsView.xaml` | + branding section with logo preview + buttons | LOW |
+| `ProfileManagementDialog.xaml` | + client logo fields | LOW |
+| `UserAccessAuditView.xaml` | + mode toggle + browse panel in left column | MEDIUM |
+| `App.xaml.cs RegisterServices()` | + 3 new registrations | LOW |
+
+Total modified files: 17

 ---

-## Build Order (Dependency Graph)
+## Build Order (Dependency-Aware)

-The following reflects the order components can be built because later items depend on earlier ones:
+The two features are independent of each other. Phases can run in parallel if worked by two developers; solo they should follow top-to-bottom order.

-```
-Phase 1: Foundation
-  └── Core/Models/* (no dependencies)
-  └── Core/Interfaces/* (no dependencies)
-  └── Core/Exceptions/* (no dependencies)
+### Phase A — Data Models (no dependencies)
+1. `Core/Models/BrandingSettings.cs` (new)
+2. `Core/Models/ReportBranding.cs` (new)
+3. `Core/Models/PagedUserResult.cs` (new)
+4. `Core/Models/TenantProfile.cs` — add nullable logo props (modification)

-Phase 2: Infrastructure Services
-  └── SettingsService (depends on Core models)
-  └── LocalizationService (depends on lang files)
-  └── DialogService (depends on WPF — implement last in phase)
-  └── AuthService / SessionManager (depends on PnP Framework NuGet)
+All files are POCOs/records. Unit-testable in isolation. No risk.

-Phase 3: Feature Services (depend on Auth + Core)
-  └── PermissionsService
-  └── StorageService
-  └── SearchService
-  └── TemplateService
-  └── DuplicateService
-  └── BulkOpsService
+### Phase B — Persistence + Service Layer
+5. `Infrastructure/Persistence/BrandingRepository.cs` (new) — depends on BrandingSettings
+6. `Services/BrandingService.cs` (new) — depends on BrandingRepository
+7. `Services/IGraphUserDirectoryService.cs` (new) — depends on PagedUserResult
+8. `Services/GraphUserDirectoryService.cs` (new) — depends on GraphClientFactory (already exists)

-Phase 4: Reporting (depends on Feature Services output models)
-  └── HtmlReportService
-  └── CsvExportService
+Unit tests for BrandingService (mock repository) and GraphUserDirectoryService (mock Graph client) can be written at this phase.

-Phase 5: ViewModels (depend on service interfaces)
-  └── MainWindowViewModel (shell, nav, tenant selector)
-  └── Feature ViewModels (Permissions, Storage, Search, Templates, Duplicates, BulkOps)
-  └── SettingsViewModel
+### Phase C — HTML Export Service Extensions
+9. All 5 `Services/Export/*HtmlExportService.cs` modifications — add optional `ReportBranding?` param

-Phase 6: Views + App Bootstrap (depend on ViewModels + DI)
-  └── XAML Views (bind to ViewModels)
-  └── Controls (TenantSelector, LogPanel, Charts)
-  └── App.xaml.cs DI container wiring
-```
+These are independent of each other. Tests: verify that passing `null` branding produces identical HTML to current output (regression), and that passing a branding record injects the expected `<img>` tags.
+
+### Phase D — ViewModel Integration (branding)
+10. `SettingsViewModel.cs` — add MSP logo commands + preview
+11. `ProfileManagementViewModel.cs` — add client logo commands + preview
+12. `PermissionsViewModel.cs` — add BrandingService injection, use in ExportHtmlAsync
+13. `StorageViewModel.cs` — same
+14. `SearchViewModel.cs` — same
+15. `DuplicatesViewModel.cs` — same
+16. `App.xaml.cs` — register BrandingRepository, BrandingService
+
+Steps 12-15 follow an identical pattern and can be batched together.
+
+### Phase E — ViewModel Integration (directory browse)
+17. `UserAccessAuditViewModel.cs` — add IGraphUserDirectoryService injection, browse mode state/commands
+
+Note: UserAccessAuditViewModel also gets BrandingService at this phase (from Phase D pattern). Do both together to avoid touching the constructor twice.
+
+### Phase F — View Layer (branding UI)
+18. `SettingsView.xaml` — add MSP branding section
+19. `ProfileManagementDialog.xaml` — add client logo fields
+
+Requires a base64-to-BitmapSource `IValueConverter` (add to `Views/Converters/`). This is a common WPF pattern — implement once, reuse in both views.
+
+### Phase G — View Layer (directory browse UI)
+20. `UserAccessAuditView.xaml` — add mode toggle + browse panel
+21. `UserAccessAuditView.xaml.cs` — add SelectionChanged handler for directory ListView
+
+This is the highest-risk UI change: the left panel is being restructured. Do this last, after all ViewModel behavior is proven by unit tests.

 ---

-## Scaling Considerations
+## Anti-Patterns to Avoid

-This is a local desktop tool with a single user. "Scaling" means handling larger SharePoint tenants, not more users.
+### Storing Logo Images as Separate Files
+**Why bad:** Breaks the single-data-folder design. Reports become non-self-contained if they reference external paths. Atomic save semantics break.
+**Instead:** Base64-encode into JSON. Logo thumbnails are typically 10-200KB. Base64 overhead (~33%) is negligible.

-| Concern | Approach |
-|---------|----------|
-| Large site collections (1000+ sites) | Async streaming with early cancellation; paginated PnP calls; virtual DataGrid |
-| Deep permission hierarchies | Configurable scan depth; user can limit scope to top-level only |
-| Large file search results | Server-side KQL filtering first, client-side regex only as secondary pass |
-| Multiple simultaneous operations | Each ViewModel has its own CancellationTokenSource; operations are isolated |
-| Session token expiry during long scan | MSAL silent refresh + retry on 401; surface error to user if re-auth needed |
+### Adding an `IHtmlExportService` Interface Just for Branding
+**Why bad:** The existing pattern is 5 concrete classes with no interfaces, consumed directly by ViewModels. Adding an interface for a parameter change creates ceremony without value.
+**Instead:** Add `ReportBranding? branding = null` as optional parameter. Existing callers compile unchanged.
+
+### Loading All Tenant Users at Once
+**Why bad:** Enterprise tenants regularly have 20,000-100,000 users. A full load blocks the UI for 30+ seconds and allocates hundreds of MB.
+**Instead:** `PagedUserResult` pattern — page 1 on mode toggle, "Load more" button, server-side filter applied to DirectoryFilter text.
+
+### Async in ViewModel Constructor
+**Why bad:** DI constructs ViewModels synchronously on the UI thread. Async work in constructors requires fire-and-forget which loses exceptions.
+**Instead:** `partial void OnIsBrowseModeActiveChanged` fires `LoadDirectoryCommand` when browse mode activates. Constructor only wires up commands and state.
+
+### Client Logo in `AppSettings` or `BrandingSettings`
+**Why bad:** Client logos are per-tenant. `AppSettings` and `BrandingSettings` are global. Mixing them makes per-profile deletion awkward and serialization structure unclear.
+**Instead:** `ClientLogoBase64` + `ClientLogoMimeType` directly on `TenantProfile` (serialized in `profiles.json`). MSP logo goes in `branding.json` via `BrandingRepository`.
+
+### Changing `BuildHtml` Signatures to Required Parameters
+**Why bad:** All 5 HTML export services currently have callers without branding. Making the parameter required is a breaking change forcing simultaneous updates across 5 VMs.
+**Instead:** `ReportBranding? branding = null` is optional. Inject only where branding is desired. Existing call sites remain unchanged.

 ---

-## Anti-Patterns
+## Scalability Considerations

-### Anti-Pattern 1: `Dispatcher.Invoke` in Services
-
-**What people do:** Call `Application.Current.Dispatcher.Invoke()` inside service classes to update UI state.
-**Why it's wrong:** Couples service layer to WPF, makes services untestable, causes deadlocks if called from wrong thread.
-**Do this instead:** Service accepts `IProgress<T>` parameter. `Progress<T>` marshals to UI thread automatically via the captured SynchronizationContext.
-
-### Anti-Pattern 2: Giant "God ViewModel"
-
-**What people do:** Create one MainViewModel with all feature logic, mirroring the monolithic PowerShell script.
-**Why it's wrong:** Replicates the exact problem being solved. Hard to navigate, hard to test, merge conflicts on every change.
-**Do this instead:** One ViewModel per feature tab. MainWindowViewModel owns only shell navigation, active tenant, and log state.
-
-### Anti-Pattern 3: Storing ClientContext as a Long-Lived Static
-
-**What people do:** Cache `ClientContext` in a static field for reuse.
-**Why it's wrong:** `ClientContext` is not thread-safe and has an auth token that expires. Static makes it impossible to manage per-tenant.
-**Do this instead:** `SessionManager` manages ClientContext lifetime. Services request a context per operation. PnP Framework handles token refresh.
-
-### Anti-Pattern 4: Blocking Async on Sync Context
-
-**What people do:** Call `.Result` or `.Wait()` on Tasks inside WPF event handlers to avoid `async void`.
-**Why it's wrong:** Deadlocks the WPF SynchronizationContext. The UI freezes permanently.
-**Do this instead:** Use `async void` only for top-level event handlers (acceptable in WPF), or bind all user actions to `AsyncRelayCommand`.
-
-### Anti-Pattern 5: Silent Catch Blocks (porting the existing bug)
-
-**What people do:** Wrap PnP calls in `catch {}` or `catch { /* ignore */ }` to prevent crashes.
-**Why it's wrong:** The existing PowerShell app has 38 such blocks — they produce silent failures, missing data, and phantom "success" states.
-**Do this instead:** Catch specific exceptions (`SharePointException`, `MicrosoftIdentityException`). Log with full stack trace via `ILogger`. Surface user-visible error message via ViewModel's `ErrorMessage` property.
-
---
-
-## Integration Points
-
-### External Services
-
-| Service | Integration Pattern | Library | Notes |
-|---------|---------------------|---------|-------|
-| SharePoint Online (CSOM) | PnP Framework `ClientContext` | `PnP.Framework` NuGet | Use for permissions, storage, templates, bulk ops |
-| SharePoint Search | PnP Framework `SearchRequest` | `PnP.Framework` NuGet | KQL queries; paginated |
-| Microsoft Graph | `GraphServiceClient` | `Microsoft.Graph` NuGet | Use for user/group lookups, Teams data |
-| Azure AD / MSAL | `PublicClientApplication` via PnP `AuthenticationManager` | Built into `PnP.Framework` | Interactive browser login; token cache callback |
-| WPF Charts | `LiveCharts2` or `OxyPlot.Wpf` | NuGet | Storage metrics visualization; LiveCharts2 preferred for richer WPF binding |
-
-### Internal Boundaries
-
-| Boundary | Communication | Notes |
-|----------|---------------|-------|
-| SessionManager ↔ Feature Services | `TenantSession` passed per operation | Services do not store sessions |
-| LocalizationService ↔ XAML | Singleton bound via `StaticResource`; properties fire `INotifyPropertyChanged` on language switch | All UI text goes through this |
-| ReportExportService ↔ ViewModels | Called after operation completes; returns file path | Self-contained HTML with embedded JS/CSS |
-| SettingsService ↔ all singletons | Read at startup; written on change | JSON format must match existing `Sharepoint_Settings.json` schema for migration |
+| Concern | Impact | Mitigation |
+|---------|--------|------------|
+| Logo storage size in JSON | PNG logos base64-encoded: 10-200KB per logo. `profiles.json` grows by at most that per tenant | Acceptable — config files, not bulk data |
+| HTML report file size | +2-10KB per logo (base64 inline) | Negligible — reports are already 100-500KB |
+| Directory browse load time | 100-user pages from Graph: ~200-500ms per page | Loading indicator, pagination. Acceptable UX. |
+| Large tenants (50k+ users) | Full load would take minutes and exceed memory budgets | Pagination via `PagedUserResult` prevents this entirely |
+| ViewModel constructor overhead | BrandingService adds one lazy JSON read at first export | Not at construction — no startup impact |

 ---

 ## Sources

- [Introduction to MVVM Toolkit - Microsoft Learn](https://learn.microsoft.com/en-us/dotnet/communitytoolkit/mvvm/) — HIGH confidence
- [AsyncRelayCommand - CommunityToolkit](https://learn.microsoft.com/en-us/dotnet/communitytoolkit/mvvm/asyncrelaycommand) — HIGH confidence
- [PnP Framework AuthenticationManager API](https://pnp.github.io/pnpframework/api/PnP.Framework.AuthenticationManager.html) — HIGH confidence
- [PnP Framework Getting Started](https://pnp.github.io/pnpframework/using-the-framework/readme.html) — HIGH confidence
- [Acquire and cache tokens with MSAL - Microsoft Learn](https://learn.microsoft.com/en-us/entra/identity-platform/msal-acquire-cache-tokens) — HIGH confidence
- [WPF Development Best Practices 2024 - MESCIUS](https://medium.com/mesciusinc/wpf-development-best-practices-for-2024-9e5062c71350) — MEDIUM confidence
- [Modern WPF Development: MVVM and Prism - Einfochips](https://www.einfochips.com/blog/modern-wpf-development-leveraging-mvvm-and-prism-for-enterprise-app/) — MEDIUM confidence
- [Async Programming Patterns for MVVM - Microsoft Learn](https://learn.microsoft.com/en-us/archive/msdn-magazine/2014/april/async-programming-patterns-for-asynchronous-mvvm-applications-commands) — HIGH confidence
+All findings are based on direct inspection of the codebase at `C:/Users/dev/Documents/projets/Sharepoint/SharepointToolbox/`. No external research needed — this is an integration architecture document for a known codebase.

---
-
-*Architecture research for: C#/WPF SharePoint Online administration desktop tool*
-*Researched: 2026-04-02*
+Key files examined:
+- `Core/Models/TenantProfile.cs`, `AppSettings.cs`
+- `Infrastructure/Persistence/ProfileRepository.cs`, `SettingsRepository.cs`
+- `Infrastructure/Auth/GraphClientFactory.cs`
+- `Services/SettingsService.cs`, `ProfileService.cs`
+- `Services/GraphUserSearchService.cs`, `IGraphUserSearchService.cs`
+- `Services/Export/HtmlExportService.cs`, `UserAccessHtmlExportService.cs`, `StorageHtmlExportService.cs`
+- `ViewModels/FeatureViewModelBase.cs`, `MainWindowViewModel.cs`
+- `ViewModels/Tabs/UserAccessAuditViewModel.cs`, `SettingsViewModel.cs`
+- `Views/Tabs/UserAccessAuditView.xaml`, `SettingsView.xaml`
+- `App.xaml.cs`
@@ -1,192 +1,211 @@
-# Feature Research
+# Feature Landscape

-**Domain:** SharePoint Online administration and auditing desktop tool (MSP / IT admin)
-**Researched:** 2026-04-02
-**Confidence:** MEDIUM (competitive landscape from web sources; no Context7 for SaaS tools; Microsoft docs HIGH confidence)
+**Domain:** MSP IT admin desktop tool — SharePoint audit report branding + user directory browse
+**Milestone:** v2.2 — Report Branding & User Directory
+**Researched:** 2026-04-08
+**Overall confidence:** HIGH (verified via official Graph API docs + direct codebase inspection)

-## Feature Landscape
+---

-### Table Stakes (Users Expect These)
+## Scope Boundary

-Features that IT admins and MSPs assume exist in any SharePoint admin tool. Missing these makes the product feel broken or incomplete.
+This file covers only the two net-new features in v2.2:
+1. HTML report branding (MSP logo + client logo per tenant)
+2. User directory browse mode in the user access audit tab
+
+Everything else is already shipped. Dependencies on existing code are called out explicitly.
+
+---
+
+## Feature 1: HTML Report Branding
+
+### Table Stakes
+
+Features an MSP admin expects without being asked. If missing, the reports feel unfinished and
+unprofessional to hand to a client.

 | Feature | Why Expected | Complexity | Notes |
 |---------|--------------|------------|-------|
-| Permissions report (site-level) | Every audit tool has this; admins must prove who has access where | MEDIUM | Must show owners, members, guests, external users, and broken inheritance |
-| Export to CSV | Standard workflow — admins paste into tickets, compliance reports, Excel | LOW | Already in current app; keep for all reports |
-| Multi-site permissions scan | Admins manage dozens of sites; per-site-only scan is unusable at scale | HIGH | Requires batching Graph API calls; throttling management needed |
-| Storage metrics per site | Native M365 admin center only shows tenant-level; per-site is expected | MEDIUM | Already in current app; retain and improve |
-| Interactive login / Azure AD OAuth | No client secret storage expected; browser-based auth is the norm | MEDIUM | Already implemented; new version adds session caching |
-| Site template management | Re-using structure across client sites is a core MSP workflow | MEDIUM | Already in current app; port to C# |
-| File search across sites | Finding content across a tenant is a day-1 admin task | MEDIUM | Already in current app; Graph driveItem search |
-| Bulk operations (user add/remove, site creation) | Manual one-by-one is unacceptable at MSP scale | HIGH | Already in current app; async required to avoid UI freeze |
-| Error reporting (not silent failures) | Admins need to know when scans fail partially | LOW | Current app has 38 silent catch blocks — critical fix |
-| Localization (EN + FR) | Already exists; removing it would break existing users | LOW | Key-based translation system already in place |
-| Export to interactive HTML | Shareable reports without requiring recipients to have the tool | MEDIUM | Already in current app; retain embedded JS for sorting/filtering |
+| MSP global logo in report header | Every white-label MSP tool shows the MSP's own brand on deliverables | Low | Single image stored in AppSettings or a dedicated branding settings section |
+| Client (per-tenant) logo in report header | MSP reports are client-facing; client should see their own logo next to the MSP's | Medium | Stored in TenantProfile; 2 sources: import from file or pull from tenant |
+| Logo renders in self-contained HTML (no external URL) | Reports are often emailed or archived; external URLs break offline | Low | Base64-encode and embed as `data:image/...;base64,...` inline in `<img src=` |
+| Logo graceful absence (no logo configured = no broken image) | Admins will run the tool before configuring logos | Trivial | Conditional render — omit the `<img>` block entirely when no logo is set |
+| Consistent placement across all HTML export types | App already ships 5+ HTML exporters; logos must appear in all of them | Medium | Extract a shared header-builder method or inject a branding context into each export service |

-### Differentiators (Competitive Advantage)
+### Differentiators

-Features that are not universally provided, or are done poorly by competitors, where this tool can create genuine advantage.
+Features not expected by default, but add meaningful value once table stakes are covered.

 | Feature | Value Proposition | Complexity | Notes |
 |---------|-------------------|------------|-------|
-| Multi-tenant session caching | MSPs switch between 10-30 client tenants daily; re-auth per client wastes 2-3 min each | HIGH | Token cache per tenant profile; MSAL token cache serialization; core MSP differentiator |
-| User access export across selected sites | "Show me everything User X can access across these 15 sites" — native M365 can't do this for arbitrary site subsets | HIGH | Requires enumerating group memberships, direct assignments, and inherited access across n sites; high Graph API volume |
-| Simplified permissions view (plain language) | Compliance reports today require admins to translate "Contribute" to "can edit files" — untrained staff can't read them | MEDIUM | Jargon-free labels, summary counts, color coding; configurable detail level |
-| Storage graph by file type (pie + bar toggle) | Native admin center shows totals only; file-type breakdown identifies what's consuming quota (videos, backups, etc.) | MEDIUM | Requires Graph driveItem enumeration with file extension grouping; recharts-style WPF chart control |
-| Duplicate file detection | Reduces storage waste; no native Microsoft tool provides this simply | HIGH | Hash-based (SHA256/MD5) or name+size matching; large tenant = Graph throttling challenge |
-| Folder structure provisioning | Create standardized folder trees on new sites from a template — critical for MSPs onboarding clients | MEDIUM | Already in current app; differentiating because competitors (ShareGate) don't focus on this |
-| Offline profile / tenant registry | Store tenant URLs, display names, notes locally — instant context switching without re-entering URLs | LOW | JSON-backed, local only — simple but missing from all SaaS tools by design |
-| Operation progress and cancellation | SaaS tools run jobs server-side; desktop tool must show real-time progress and allow cancel mid-scan | MEDIUM | CancellationToken throughout async operations; progress reporting via IProgress<T> |
+| Auto-pull client logo from Microsoft Entra tenant branding | Zero-config for tenants that already have a banner logo set in Entra ID | Medium | Graph API: `GET /organization/{id}/branding/localizations/default/bannerLogo` returns raw image bytes. Least-privileged scope is `User.Read` (delegated, already in use). Returns empty body or 404 when not configured — must handle gracefully. |
+| Report timestamp and tenant display name in header | Contextualizes archived reports without needing to inspect the filename | Low | TenantProfile.TenantUrl already available; display name derivable from domain |

-### Anti-Features (Commonly Requested, Often Problematic)
+### Anti-Features

-Features that seem valuable but create disproportionate complexity, maintenance burden, or scope creep for this tool's purpose.
+Do not build these. They add scope without proportionate MSP value.

-| Feature | Why Requested | Why Problematic | Alternative |
-|---------|---------------|-----------------|-------------|
-| Permission change alerts / real-time monitoring | Admins want to know when permissions change | Requires persistent background service, webhook registration in Azure, certificate lifecycle management — turns a desktop tool into a service | Run scheduled audit scans manually or via Windows Task Scheduler; export diffs between runs |
-| Automated remediation (auto-revoke permissions) | "Fix it for me" saves time | One wrong rule destroys access for a client's entire org; liability risk; requires undo capability and audit trail that equals a full compliance system | Surface recommendations, let admin click to apply one at a time |
-| SQLite or database storage | Faster queries on large datasets | Adds install dependency, schema migration complexity, and breaks the "single EXE" distribution model | JSON with chunked loading; lazy evaluation; paginated display |
-| Cloud sync / shared tenant registry | Team of admins sharing tenant configs | Requires auth system, conflict resolution, server infrastructure — out of scope for local tool | Export/import JSON profiles; share config files manually |
-| AI-powered governance recommendations | Microsoft is adding this to native admin center (SharePoint Admin Agent, Copilot-licensed) | Requires Copilot license, Graph calls with high latency, and competes directly with Microsoft's own roadmap | Focus on raw data accuracy and export quality; let Microsoft handle AI summaries |
-| Cross-platform (Mac/Linux) support | Some admins use Macs | WPF is Windows-only; rewrite to MAUI/Avalonia is a full project — not justified for current user base | Confirmed out of scope in PROJECT.md |
-| Version history management / rollback | Admins sometimes need to see version bloat | Version management is a deep separate problem; Graph API pagination for versions is complex and slow at scale | Surface version storage totals in storage metrics; flag libraries with high version counts |
-| SharePoint content migration | Admins ask to move content between tenants or sites | Migration is a fully separate product category (ShareGate, AvePoint); competing here is a multi-year investment | Refer to ShareGate or native SharePoint migration for content moves |
+| Anti-Feature | Why Avoid | What to Do Instead |
+|--------------|-----------|-------------------|
+| Color theme / CSS customization per tenant | Complexity explodes — per-tenant CSS is a design system problem, not an admin tool feature | Stick to a single professional neutral theme; logo is sufficient branding |
+| PDF export with embedded logo | PDF generation requires a third-party library (iTextSharp, QuestPDF, etc.) adding binary size to the 200 MB EXE | Document in release notes that users can print-to-PDF from browser |
+| Animated or SVG logo support | MIME handling complexity; SVG in data-URIs introduces XSS risk | Support PNG/JPG/GIF only; reject SVG at import time |
+| Logo URL field (hotlinked) | Reports break when URL becomes unavailable; creates external dependency for a local-first tool | Force file import with base64 embedding |

-## Feature Dependencies
+### Feature Dependencies

 ```
-Multi-tenant session caching
-    └──requires──> Tenant profile registry (JSON-backed)
-                       └──required by──> All features (auth gate)
-
-User access export across selected sites
-    └──requires──> Multi-site permissions scan
-                       └──requires──> Multi-tenant session caching
-
-Simplified permissions view
-    └──enhances──> Permissions report (site-level)
-    └──enhances──> User access export across selected sites
-
-Storage graph by file type
-    └──requires──> Storage metrics per site
-    └──requires──> Graph driveItem enumeration (file extension data)
-
-Duplicate file detection
-    └──requires──> File search across sites (file enumeration infrastructure)
-    └──conflicts──> Automated remediation (deletion without undo = data loss risk)
-
-Bulk operations
-    └──requires──> Operation progress and cancellation
-    └──requires──> Error reporting (not silent failures)
-
-Export (CSV / HTML)
-    └──enhances──> All report features
-    └──required by──> Compliance audit workflows
-
-Folder structure provisioning
-    └──requires──> Site template management
+AppSettings              + MspLogoBase64 (string?, nullable)
+TenantProfile            + ClientLogoBase64 (string?, nullable)
+                         + ClientLogoSource (enum: None | Imported | AutoPulled)
+Shared branding helper   → called by HtmlExportService, UserAccessHtmlExportService,
+                            StorageHtmlExportService, DuplicatesHtmlExportService,
+                            SearchHtmlExportService
+Auto-pull code path      → Graph API call via existing GraphClientFactory
+Logo import UI           → WPF OpenFileDialog -> File.ReadAllBytes -> Convert.ToBase64String
+                            -> stored in profile JSON via existing ProfileRepository
 ```

-### Dependency Notes
+**Key existing code note:** All 5+ HTML export services currently build their `<body>` independently
+with no shared header. Branding requires one of:
+- (a) a `ReportBrandingContext` record passed into each exporter's `BuildHtml` method, or
+- (b) a `HtmlReportHeaderBuilder` static/injectable helper all exporters call.

- **Multi-tenant session caching requires Tenant profile registry:** Without a registry of tenant URLs and display names, the session cache has nothing to key against. The tenant profile JSON must exist before any feature can authenticate.
- **User access export requires multi-site permissions scan:** The "all accesses for user X" feature is essentially a filtered multi-site permissions scan. The scanning infrastructure must exist first.
- **Simplified permissions view enhances reports:** This is a presentation layer on top of raw permissions data — it cannot exist without the underlying data model.
- **Storage graph by file type requires Graph driveItem enumeration:** The native Graph storage reports do not include file type breakdown. This requires enumerating files with their extensions, which is a heavier Graph operation than summary-only calls.
- **Duplicate detection requires file enumeration infrastructure:** The file search feature already enumerates files; duplicate detection reuses that path but adds hash computation or name+size matching on top.
- **Bulk operations require cancellation support:** Long-running bulk operations that cannot be cancelled will freeze or force-kill the app. CancellationToken must be threaded through before bulk ops are exposed to users.
- **Duplicate detection conflicts with automated remediation:** Surfacing duplicates is safe; auto-deleting them without undo is not. Keep these concerns separate.
+Option (b) is lower risk — it does not change method signatures that existing unit tests already call.

-## MVP Definition
+### Complexity Assessment

-### Launch With (v1)
+| Sub-task | Complexity | Reason |
+|----------|------------|--------|
+| AppSettings + TenantProfile model field additions | Low | Trivial nullable-string fields; JSON serialization already in place |
+| Settings UI: MSP logo upload + preview | Low | WPF OpenFileDialog + BitmapImage from base64, standard pattern |
+| ProfileManagementDialog: client logo upload per tenant | Low | Same pattern as MSP logo |
+| Shared HTML header builder with logo injection | Low-Medium | One helper; replaces duplicated header HTML in 5 exporters |
+| Auto-pull from Entra `bannerLogo` endpoint | Medium | Async Graph call; must handle 404, empty stream, no branding configured |
+| Localization keys EN/FR for new labels | Low | ~6-10 new keys; 220+ already managed |

-Minimum viable product — sufficient to replace the existing PowerShell tool completely.
+---

- [ ] Tenant profile registry with multi-tenant session caching — without this, no feature works
- [ ] Permissions report (site-level) with CSV + HTML export — core audit use case
- [ ] Storage metrics per site — currently used daily
- [ ] File search across sites — currently used daily
- [ ] Bulk operations (member add, site creation, transfer) with progress + cancel — currently used; async required
- [ ] Site template management — core MSP provisioning workflow
- [ ] Folder structure provisioning — paired with templates
- [ ] Duplicate file detection — currently used for storage cleanup
- [ ] Error reporting (no silent failures) — current app's biggest reliability issue
- [ ] Localization (EN/FR) — existing users depend on this
+## Feature 2: User Directory Browse Mode

-### Add After Validation (v1.x)
+### Table Stakes

-Features to add once core parity is confirmed working.
+Features an admin expects when a "browse all users" mode is offered alongside the existing search.

- [ ] User access export across selected sites — new feature; high value for MSP audits; add once multi-site scan is stable
- [ ] Simplified permissions view (plain language) — presentation enhancement; add after raw data model is solid
- [ ] Storage graph by file type (pie + bar toggle) — visualization enhancement on top of existing storage metrics
+| Feature | Why Expected | Complexity | Notes |
+|---------|--------------|------------|-------|
+| Full directory listing (all member users, paginated) | Browse implies seeing everyone, not just name-search hits | Medium | Graph `GET /users` with `$top=100`, follow `@odata.nextLink` until null. Max page size is 999 but 100 pages give better progress feedback |
+| Searchable/filterable within the loaded list | Once loaded, admins filter locally without re-querying | Low | In-memory filter on DisplayName, UPN, Mail — same pattern used in PermissionsView DataGrid |
+| Sortable columns (Name, UPN) | Standard expectation for any directory table | Low | WPF DataGrid column sorting, already used in other tabs |
+| Select user from list to run access audit | The whole point — browse replaces the people-picker for users the admin cannot spell | Low | Bind selected item; reuse the existing IUserAccessAuditService pipeline unchanged |
+| Loading indicator with progress count | Large tenants (5k+ users) take several seconds to page through | Low | Existing OperationProgress pattern; show "Loaded X users..." counter |
+| Toggle between Browse mode and Search (people-picker) mode | Search is faster for known users; browse is for discovery | Low | RadioButton or ToggleButton in the tab toolbar; visibility-toggle two panels |

-### Future Consideration (v2+)
+### Differentiators

-Features to defer until product-market fit is established.
+| Feature | Value Proposition | Complexity | Notes |
+|---------|-------------------|------------|-------|
+| Filter by account type (member vs guest) | MSPs care about guest proliferation; helps scope audit targets | Low | Graph returns `userType` field; add a toggle filter. Include in `$select` |
+| Department / Job Title columns | Helps identify the right user in large tenants with common names | Low-Medium | Include `department`, `jobTitle` in `$select`; optional columns in DataGrid |
+| Session-scoped directory cache | Avoids re-fetching full tenant list on every tab visit | Medium | Store list in ViewModel or session-scoped service; invalidate on TenantSwitchedMessage |

- [ ] Scheduled scan runs via Windows Task Scheduler integration — requires stable CLI/headless mode first
- [ ] Permission comparison between two points in time (diff report) — useful for compliance but requires snapshot storage
- [ ] Export to XLSX (full Excel format, not just CSV) — requested but not critical; CSV opens in Excel adequately
+### Anti-Features

-## Feature Prioritization Matrix
+| Anti-Feature | Why Avoid | What to Do Instead |
+|--------------|-----------|-------------------|
+| Eager load on tab open | Large tenants (10k+ users) block UI and risk Graph throttling on every tab navigation | Lazy-load on explicit "Load Directory" button click; show a clear affordance |
+| Delta query / incremental sync | Delta queries are for maintaining a local replica over time; wrong pattern for a one-time audit session | Single paginated GET per session; add a Refresh button |
+| Multi-user bulk select for simultaneous audit | The audit pipeline is per-user by design; multi-user requires a fundamentally different results model | Out of scope; single-user selection only |
+| Export the user directory to CSV | That is an identity reporting feature (AdminDroid et al.), not an access audit feature | Out of scope for this milestone |
+| Show disabled accounts by default | Disabled users do not have active SharePoint access; pollutes the list for audit purposes | Default `$filter=accountEnabled eq true`; optionally expose a toggle |

-| Feature | User Value | Implementation Cost | Priority |
-|---------|------------|---------------------|----------|
-| Tenant profile registry + session caching | HIGH | MEDIUM | P1 |
-| Permissions report (site-level) | HIGH | MEDIUM | P1 |
-| Storage metrics per site | HIGH | MEDIUM | P1 |
-| File search across sites | HIGH | MEDIUM | P1 |
-| Bulk operations with progress/cancel | HIGH | HIGH | P1 |
-| Error reporting (no silent failures) | HIGH | LOW | P1 |
-| Site template management | HIGH | MEDIUM | P1 |
-| Folder structure provisioning | MEDIUM | MEDIUM | P1 |
-| Duplicate file detection | MEDIUM | HIGH | P1 |
-| Localization (EN/FR) | MEDIUM | LOW | P1 |
-| User access export across selected sites | HIGH | HIGH | P2 |
-| Simplified permissions view | HIGH | MEDIUM | P2 |
-| Storage graph by file type | MEDIUM | MEDIUM | P2 |
-| Permission diff / snapshot comparison | MEDIUM | HIGH | P3 |
-| XLSX export | LOW | LOW | P3 |
-| Scheduled scans (headless/CLI) | LOW | HIGH | P3 |
+### Feature Dependencies

-**Priority key:**
- P1: Must have for v1 launch (parity with existing PowerShell tool)
- P2: Should have — add after v1 validated; new features from PROJECT.md active requirements
- P3: Nice to have, future consideration
+```
+New IGraphDirectoryService + GraphDirectoryService
+  → GET /users?$select=displayName,userPrincipalName,mail,jobTitle,department,userType
+              &$filter=accountEnabled eq true
+              &$top=100
+  → Follow @odata.nextLink in a loop until null
+  → Uses existing GraphClientFactory (DI, unchanged)

-## Competitor Feature Analysis
+UserAccessAuditViewModel additions:
+  + IsBrowseMode (bool property, toggle)
+  + DirectoryUsers (ObservableCollection<GraphUserResult> or new DirectoryUserEntry model)
+  + DirectoryFilterText (string, filters in-memory)
+  + LoadDirectoryCommand (async, cancellable)
+  + IsDirectoryLoading (bool)
+  + SelectedDirectoryUser → feeds into existing audit execution path

-| Feature | ShareGate | ManageEngine SharePoint Manager Plus | AdminDroid | Our Approach |
-|---------|-----------|---------------------------------------|------------|--------------|
-| Permissions matrix report | Yes — visual matrix, CSV export | Yes — granular permission level reports | Yes — site users/groups report | Yes — with plain-language layer on top |
-| Multi-tenant management | Yes — SaaS, per-tenant login | Yes — web-based | Yes — cloud SaaS | Yes — local session cache, instant switch, offline profiles |
-| Storage reporting | Basic | Basic tenant-level | Basic | Enhanced — file-type breakdown, pie/bar toggle |
-| Duplicate detection | No | No | No | Yes — differentiator |
-| Folder structure provisioning | No | No | No | Yes — differentiator |
-| Site templates | Migration focus | No | No | Yes — admin provisioning focus |
-| Bulk operations | Yes — migration-focused | Limited | No | Yes — admin-operations focus (not migration) |
-| User access export (cross-site) | Partial — site-by-site | Partial | Partial | Yes — arbitrary site subset, single export |
-| Plain language permissions | No | No | No | Yes — differentiator for untrained users |
-| Local desktop app (no SaaS) | No — cloud | No — cloud | No — cloud | Yes — core constraint and privacy advantage |
-| Offline / no internet needed | No | No | No | Yes (after auth token cached) |
-| Price | ~$6K/year | Subscription | Subscription | Tool cost (one-time dev, distributed free or licensed) |
+TenantSwitchedMessage handler in ViewModel: clear DirectoryUsers, reset IsBrowseMode
+
+UserAccessAuditView.xaml:
+  + Toolbar toggle (Search | Browse)
+  + Visibility-collapsed people-picker panel when in browse mode
+  + New DataGrid panel for browse mode
+```
+
+**Key existing code note:** `GraphUserSearchService` does filtered search only (`startsWith` filter +
+`ConsistencyLevel: eventual`). Directory listing is a different call pattern — no filter, plain
+pagination without `ConsistencyLevel`. A separate `GraphDirectoryService` is cleaner than extending
+the existing service; search and browse have different cancellation and retry needs.
+
+### Complexity Assessment
+
+| Sub-task | Complexity | Reason |
+|----------|------------|--------|
+| IGraphDirectoryService + GraphDirectoryService (pagination loop) | Low-Medium | Standard Graph paging; same GraphClientFactory in DI |
+| ViewModel additions (browse toggle, load command, filter, loading state) | Medium | New async command with progress, cancellation on tenant switch |
+| View XAML: toggle + browse DataGrid panel | Medium | Visibility-toggle two panels; DataGrid column definitions |
+| In-memory filter + column sort | Low | DataGrid pattern already used in PermissionsView |
+| Loading indicator integration | Low | OperationProgress + IsLoading used by every tab |
+| Localization keys EN/FR | Low | ~8-12 new keys |
+| Unit tests for GraphDirectoryService | Low | Same mock pattern as GraphUserSearchService tests |
+| Unit tests for ViewModel browse mode | Medium | Async load command, pagination mock, filter behavior |
+
+---
+
+## Cross-Feature Dependencies
+
+Both features touch the same data models. Changes must be coordinated:
+
+```
+TenantProfile model — gains fields for branding (ClientLogoBase64, ClientLogoSource)
+AppSettings model   — gains MspLogoBase64
+ProfileRepository   — serializes/deserializes new TenantProfile fields (JSON, backward-compat)
+SettingsRepository  — serializes/deserializes new AppSettings field
+GraphClientFactory  — used by both features (no changes needed)
+TenantSwitchedMessage — consumed by UserAccessAuditViewModel to clear directory cache
+```
+
+Neither feature requires new NuGet packages. The Graph SDK, MSAL, and System.Text.Json are
+already present. No new binary dependencies means no EXE size increase.
+
+---
+
+## MVP Recommendation
+
+Build in this order, each independently releasable:
+
+1. **MSP logo in HTML reports** — highest visible impact, lowest complexity. AppSettings field + Settings UI upload + shared header builder.
+2. **Client logo in HTML reports (import from file)** — completes the co-branding pattern. TenantProfile field + ProfileManagementDialog upload UI.
+3. **User directory browse (load + select + filter)** — core browse UX. Toggle, paginated load, in-memory filter, pipe into existing audit.
+4. **Auto-pull client logo from Entra branding** — differentiator, zero-config polish. Build after manual import works so the fallback path is proven.
+5. **Directory: guest filter + department/jobTitle columns** — low-effort differentiators; add after core browse is stable.
+
+Defer to a later milestone:
+- Directory session caching across tab switches — a Refresh button is sufficient for v2.2.
+- Logo on CSV exports — CSV has no image support; not applicable.
+
+---

 ## Sources

- [ShareGate SharePoint audit tool feature page](https://sharegate.com/sharepoint-audit-tool) — MEDIUM confidence (marketing page)
- [ManageEngine SharePoint Manager Plus permissions auditing](https://www.manageengine.com/sharepoint-management-reporting/sharepoint-permission-auditing-tool.html) — MEDIUM confidence
- [Microsoft Data access governance reports — site permissions for users](https://learn.microsoft.com/en-us/sharepoint/data-access-governance-site-permissions-users-report) — HIGH confidence
- [Microsoft SharePoint Advanced Management overview](https://learn.microsoft.com/en-us/sharepoint/advanced-management) — HIGH confidence
- [sprobot.io: 9 must-have features for SharePoint storage reporting](https://www.sprobot.io/blog/how-to-choose-the-right-sharepoint-storage-reporting-tool-9-must-have-features) — MEDIUM confidence
- [AdminDroid SharePoint Online auditing](https://admindroid.com/microsoft-365-sharepoint-online-auditing) — MEDIUM confidence
- [CIAOPS: Best ways to monitor and audit permissions across SharePoint M365](https://blog.ciaops.com/2025/04/27/best-ways-to-monitor-and-audit-permissions-across-a-sharepoint-environment-in-microsoft-365/) — MEDIUM confidence
- [ShareGate: How to generate a SharePoint user permissions report](https://sharegate.com/blog/build-the-perfect-sharepoint-permissions-report) — MEDIUM confidence
- [Microsoft SharePoint storage reports admin center](https://learn.microsoft.com/en-us/microsoft-365/admin/activity-reports/sharepoint-storage-reports?view=o365-worldwide) — HIGH confidence
-
---
-*Feature research for: SharePoint Online administration/auditing desktop tool (C#/WPF, MSP/IT admin)*
-*Researched: 2026-04-02*
+- Graph API List Users (v1.0 official): https://learn.microsoft.com/en-us/graph/api/user-list?view=graph-rest-1.0 — HIGH confidence
+- Graph API Get organizationalBranding (v1.0 official): https://learn.microsoft.com/en-us/graph/api/organizationalbranding-get?view=graph-rest-1.0 — HIGH confidence
+- Graph API bannerLogo stream: `GET /organization/{id}/branding/localizations/default/bannerLogo` — HIGH confidence (verified in official docs)
+- Graph pagination concepts: https://learn.microsoft.com/en-us/graph/paging — HIGH confidence
+- ControlMap co-branding (MSP + client logo pattern): https://help.controlmap.io/hc/en-us/articles/24174398424347 — MEDIUM confidence
+- ManageEngine ServiceDesk Plus MSP per-account branding: https://www.manageengine.com/products/service-desk-msp/rebrand.html — MEDIUM confidence
+- SolarWinds MSP report customization: http://allthings.solarwindsmsp.com/2013/06/customize-your-branding-on-client.html — MEDIUM confidence
+- Direct codebase inspection: HtmlExportService.cs, GraphUserSearchService.cs, AppSettings.cs, TenantProfile.cs — HIGH confidence
@@ -381,3 +381,422 @@ File I/O is not inherently thread-safe. `System.Text.Json`'s `JsonSerializer.Ser

 *Pitfalls research for: C#/WPF SharePoint Online administration desktop tool (PowerShell-to-C# rewrite)*
 *Researched: 2026-04-02*
+
+---
+---
+
+# v2.2 Pitfalls: Report Branding & User Directory
+
+**Milestone:** v2.2 — HTML report branding (MSP/client logos) + user directory browse mode
+**Researched:** 2026-04-08
+**Confidence:** HIGH for logo handling and Graph pagination (multiple authoritative sources); MEDIUM for print CSS specifics (verified via MDN/W3C but browser rendering varies)
+
+These pitfalls are specific to adding logo branding to the existing HTML export services and replacing the people-picker search with a full directory browse mode. They complement the v1.0 foundation pitfalls above.
+
+---
+
+## Critical Pitfalls (v2.2)
+
+### Pitfall v2.2-1: Base64 Logo Encoding Bloats Every Report File
+
+**What goes wrong:**
+The five existing HTML export services (`HtmlExportService`, `UserAccessHtmlExportService`, `StorageHtmlExportService`, `SearchHtmlExportService`, `DuplicatesHtmlExportService`) are self-contained by design — no external dependencies. The natural instinct is to embed logos as inline `data:image/...;base64,...` strings in the `<style>` or `<img src>` tag of every report. This works, but base64 encoding inflates image size by ~33%. A 200 KB PNG logo becomes 267 KB of base64 text, inlined into every single exported HTML file. An MSP generating 10 reports per client per month accumulates significant bloat per file, and the logo data is re-read, re-encoded, and re-concatenated into the `StringBuilder` on every export call.
+
+The secondary problem is that `StringBuilder.AppendLine` with a very long base64 string (a 500 KB logo becomes ~667 KB of text) causes a single string allocation of that size per report, wasted immediately after the file is written.
+
+**Why it happens:**
+The "self-contained HTML" design goal (no external files) is correct for portability. Developers apply it literally and embed every image inline. They test with a small 20 KB PNG and never notice. Production logos from clients are often 300–600 KB originals.
+
+**Consequences:**
+- Report files 300–700 KB larger than necessary — not catastrophic, but noticeable when opening in a browser.
+- Logo bytes are re-allocated in memory on every export call — fine for occasional use, wasteful in batch scenarios.
+- If the same logo is stored in `AppSettings` or `TenantProfile` as a raw file path, it is read from disk and re-encoded on every export. File I/O error at export time if the path is invalid.
+
+**Prevention:**
+1. Enforce a file size limit at import time: reject logos > 512 KB. Display a warning in the settings UI. This keeps base64 strings under ~700 KB worst case.
+2. Cache the base64 string. Store it in the `AppSettings`/`TenantProfile` model as the pre-encoded base64 string (not the original file path), so it is computed once on import and reused on every export. `TenantProfile` and `AppSettings` already serialize to JSON — base64 strings serialize cleanly.
+3. Enforce image dimensions in the import UI: warn if the image is wider than 800 px and suggest the user downscale. A 200×60 px logo at 72 dpi is sufficient for an HTML report header.
+4. When reading from the JSON-persisted base64 string, do not re-decode and re-encode. Inject it directly into the `<img src="data:image/png;base64,{cachedBase64}">` tag.
+
+**Detection:**
+- Export a report and check the generated HTML file size. If it is > 100 KB before any data rows are added, the logo is too large.
+- Profile `BuildHtml` with a 500 KB logo attached — memory allocation spike is visible in the .NET diagnostic tools.
+
+**Phase to address:** Logo import/settings phase. The size validation and pre-encoding strategy must be established before any export service is modified to accept logo parameters. If the export services are modified first with raw file-path injection, every caller must be updated again later.
+
+---
+
+### Pitfall v2.2-2: Graph API Full Directory Listing Requires Explicit Pagination — 999-User Hard Cap Per Page
+
+**What goes wrong:**
+The existing `GraphUserSearchService` uses `$filter` with `startsWith` and `$top=10` — a narrow search, not a full listing. The new user directory browse mode needs to fetch all users in a tenant. Graph API `GET /users` returns a maximum of 999 users per page (not 1000 — the valid range for `$top` is 1–999). Without explicit pagination using `@odata.nextLink`, the call silently returns at most 999 users regardless of tenant size. A 5 000-user tenant appears to have 999 users in the directory with no error or indication of truncation.
+
+**Why it happens:**
+Developers see `$top=999` and assume a single call returns everything for "normal" tenants. The Graph SDK's `.GetAsync()` call returns a `UserCollectionResponse` with a `Value` list and an `OdataNextLink` property. If `OdataNextLink` is not checked, pagination stops after the first page. The existing `SearchUsersAsync` intentionally returns only 10 results — the pagination concern was never encountered there.
+
+**Consequences:**
+- The directory browse mode silently shows fewer users than the tenant contains.
+- An MSP auditing a 3 000-user client tenant sees only 999 users with no warning.
+- Guest/service accounts in the first 999 may appear; those after page 1 are invisible.
+
+**Prevention:**
+Use the Graph SDK's `PageIterator<User, UserCollectionResponse>` for all full directory fetches. This is the Graph SDK's built-in mechanism for transparent pagination:
+
+```csharp
+var users = new List<User>();
+var response = await graphClient.Users.GetAsync(config =>
+{
+    config.QueryParameters.Select = new[] { "displayName", "userPrincipalName", "mail", "userType" };
+    config.QueryParameters.Top = 999;
+    config.QueryParameters.Orderby = new[] { "displayName" };
+}, ct);
+
+var pageIterator = PageIterator<User, UserCollectionResponse>.CreatePageIterator(
+    graphClient,
+    response,
+    user => { users.Add(user); return true; },
+    request => { request.Headers.Add("ConsistencyLevel", "eventual"); return request; });
+
+await pageIterator.IterateAsync(ct);
+```
+
+Always pass `CancellationToken` through the iterator. For tenants with 10 000+ users, this will make multiple sequential API calls — surface progress to the user ("Loading directory... X users loaded").
+
+**Detection:**
+- Request `$count=true` with `ConsistencyLevel: eventual` on the first page call. Compare the returned `@odata.count` to the number of items received after full iteration. If they differ, pagination was incomplete.
+- Test against a tenant with > 1 000 users before shipping the directory browse feature.
+
+**Phase to address:** User directory browse implementation phase. The interface `IGraphUserSearchService` will need a new method `GetAllUsersAsync` alongside the existing `SearchUsersAsync` — do not collapse them.
+
+---
+
+### Pitfall v2.2-3: Graph API Directory Listing Returns Guest, Service, and Disabled Accounts Without Filtering
+
+**What goes wrong:**
+`GET /users` returns all user objects in the tenant: active members, disabled accounts, B2B guest users (`userType eq 'Guest'`), on-premises sync accounts, and service/bot accounts. In an MSP context, a client's SharePoint tenant may have dozens of guest users from external collaborators and several service accounts (e.g., `sharepoint@clientdomain.com`, `MicrosoftTeams@clientdomain.com`). If the directory browse mode shows all 3 000 raw entries, admins spend time scrolling past noise to find real staff.
+
+Filtering on `userType` helps for guests but there is no clean Graph filter for "service accounts" — it is a convention, not a Graph property. There is also no Graph filter for disabled accounts from the basic `$filter` syntax without `ConsistencyLevel: eventual`.
+
+**Why it happens:**
+The people-picker search in v1.1 is text-driven — the user types a name, noise is naturally excluded. A browse mode showing all users removes that implicit filter and exposes the raw directory.
+
+**Consequences:**
+- Directory appears larger and noisier than expected for MSP clients.
+- Admin selects the wrong account (service account instead of user) and runs an audit that returns no meaningful results.
+- Guest accounts from previous collaborations appear as valid targets.
+
+**Prevention:**
+Apply a default filter in the directory listing that excludes obvious non-staff entries, while allowing the user to toggle the filter off:
+- Default: `$filter=accountEnabled eq true and userType eq 'Member'` — this excludes guests and disabled accounts. Requires no `ConsistencyLevel` header (supported in standard filter mode).
+- Provide a checkbox in the directory browse UI: "Include guest accounts" that adds `or userType eq 'Guest'` to the filter.
+- For service account noise: apply a client-side secondary filter that hides entries where `displayName` contains common service patterns (`SharePoint`, `Teams`, `No Reply`, `Admin`) — this is a heuristic and should be opt-in, not default.
+
+Note: filtering `accountEnabled eq true` in the `$filter` parameter without `ConsistencyLevel: eventual` works on the v1.0 `/users` endpoint. Verify before release.
+
+**Detection:**
+- Count the raw user total vs. the filtered total for a test tenant. If they differ by more than 20%, the default filter is catching real users — review the filter logic.
+
+**Phase to address:** User directory browse implementation phase, before the UI is built. The filter strategy must be baked into the service interface so the ViewModel does not need to know about it.
+
+---
+
+### Pitfall v2.2-4: Full Directory Load Hangs the UI Without Progress Feedback
+
+**What goes wrong:**
+Fetching 3 000 users with page iteration takes 3–8 seconds depending on tenant size and Graph latency. The existing people-picker search is a debounced 500 ms call that returns quickly. The directory browse "Load All" operation is fundamentally different in character. Without progress feedback, the user sees a frozen list and either waits or clicks the button again (triggering a second concurrent load).
+
+The existing `IsBusy` / `IsRunning` pattern on `AsyncRelayCommand` will disable the button, but there is no count feedback in the existing ViewModel pattern for this case.
+
+**Why it happens:**
+Developers implement the API call first, wire it to a button, and test with a 50-user dev tenant where it returns in < 500 ms. The latency problem is only discovered when testing against a real client.
+
+**Consequences:**
+- On first use with a large tenant, the admin thinks the feature is broken and restarts the app.
+- If the command is not properly guarded, double-clicks trigger two concurrent Graph requests populating the same `ObservableCollection`.
+
+**Prevention:**
+- Add a `DirectoryLoadStatus` observable property: `"Loading... X users"` updated via `IProgress<int>` inside the `PageIterator` callback.
+- Use `BindingOperations.EnableCollectionSynchronization` on the users `ObservableCollection` so items can be streamed in as each page arrives rather than waiting for full iteration.
+- The `AsyncRelayCommand` `CanExecute` must return `false` while loading is in progress (the toolkit does this automatically when `IsRunning` is true — verify it is wired).
+- Add a cancellation button that is enabled during the load, using the same `CancellationToken` passed to `PageIterator.IterateAsync`.
+
+**Detection:**
+- Test with a mock that simulates 10 pages of 999 users each, adding a 200 ms delay between pages. The UI should show incrementing count feedback throughout.
+
+**Phase to address:** User directory browse ViewModel phase.
+
+---
+
+### Pitfall v2.2-5: Logo File Format Validation Is Skipped, Causing Broken Images in Reports
+
+**What goes wrong:**
+The `OpenFileDialog` filter (`*.png;*.jpg;*.jpeg`) prevents selecting a `.exe` file, but it does not validate that the selected file is actually a valid image. A user may select a file that was renamed with a `.png` extension but is actually a PDF, a corrupted download, or an SVG (which is XML text, not a binary image format). When the file is read and base64-encoded, the string is valid base64, but the browser renders a broken image icon in the HTML report.
+
+WPF's `BitmapImage` will throw an exception on corrupt or unsupported binary files. SVG files loaded as a `BitmapImage` throw because SVG is not a WPF-native raster format.
+
+A second failure mode: `BitmapImage` throws `NotSupportedException` or `FileFormatException` for EXIF-corrupt JPEGs. This is a known .NET issue where WPF's BitmapImage is strict about EXIF metadata validity.
+
+**Why it happens:**
+The file picker filter is treated as sufficient validation. EXIF corruption is not anticipated because it is invisible to casual inspection.
+
+**Consequences:**
+- Report is generated successfully from the app's perspective, but every page has a broken image icon where the logo should appear.
+- The user does not see the error until they open the HTML file.
+- EXIF-corrupt JPEG from a phone camera or scanner is a realistic scenario in an MSP workflow.
+
+**Prevention:**
+After file selection and before storing the path or encoding:
+1. Load the file as a `BitmapImage` in a `try/catch`. If it throws, reject the file and show a user-friendly error: "The selected file could not be read as an image. Please select a valid PNG or JPEG file."
+2. Check `BitmapImage.PixelWidth` and `PixelHeight` after load — a 0×0 image is invalid.
+3. For EXIF-corrupt JPEGs: `BitmapCreateOptions.IgnoreColorProfile` and `BitmapCacheOption.OnLoad` reduce (but do not eliminate) EXIF-related exceptions. Wrap the load in a retry with these options if the initial load fails.
+4. Do not accept SVG files. The file filter should explicitly include only `*.png;*.jpg;*.jpeg;*.bmp;*.gif`. SVG requires a third-party library (e.g., SharpVectors) to rasterize — out of scope for this milestone.
+5. After successful load, verify the resulting base64 string decodes back to a valid image (round-trip check) before persisting to JSON.
+
+**Detection:**
+- Unit test: attempt to load a `.txt` file renamed to `.png` and a known EXIF-corrupt JPEG. Verify both are rejected with a user-visible error, not a silent crash.
+
+**Phase to address:** Logo import/settings phase. Validation must be in place before the logo path or base64 is persisted.
+
+---
+
+### Pitfall v2.2-6: Logo Path Stored in JSON Settings Becomes Stale After EXE Redistribution
+
+**What goes wrong:**
+The simplest implementation of logo storage is to persist the file path (`C:\Users\admin\logos\msp-logo.png`) in `AppSettings` JSON. This works on the machine where the logo was imported. When the tool is redistributed to another MSP technician (or when the admin reinstalls Windows), the path no longer exists. The export service reads the path, the file is missing, and the logo is silently omitted from new reports — or worse, throws an unhandled `FileNotFoundException`.
+
+**Why it happens:**
+Path storage is the simplest approach. Base64 storage feels "heavy." The problem is only discovered when a colleague opens the tool on their own machine.
+
+**Consequences:**
+- Client-branded reports stop including the logo without any warning.
+- The user does not know the logo is missing until a client complains about the unbranded report.
+- The `AppSettings.DataFolder` pattern is already established in the codebase — the team may assume all assets follow the same pattern, but logos are user-supplied files, not app-generated data.
+
+**Prevention:**
+Store logos as base64 strings directly in `AppSettings` and `TenantProfile` JSON, not as file paths. The import action reads the file once, encodes it, stores the string, and the original file path is discarded after import. This makes the settings file fully portable across machines.
+
+The concern about JSON file size is valid but manageable: a 512 KB PNG becomes ~700 KB of base64, which increases the settings JSON file by that amount. For a tool that already ships as a 200 MB EXE, a 1 MB settings file is acceptable. Document this design decision explicitly.
+
+Alternative if file-path storage is preferred: copy the logo file into a `logos/` subdirectory of `AppSettings.DataFolder` at import time (use a stable filename like `msp-logo.png`), store only the relative path in JSON, and resolve it relative to `DataFolder` at export time. This is portable as long as the DataFolder travels with the settings.
+
+**Detection:**
+- After importing a logo, manually edit `AppSettings.json` and verify the logo data is stored correctly.
+- Move the settings JSON to a different machine and verify a report is generated with the logo intact.
+
+**Phase to address:** Logo import/settings phase. The storage strategy must be decided and implemented before any export service accepts logo data.
+
+---
+
+## Moderate Pitfalls (v2.2)
+
+### Pitfall v2.2-7: Logo Breaks HTML Report Print Layout
+
+**What goes wrong:**
+The existing HTML export services produce print-friendly reports (flat tables, no JavaScript required for static reading). Adding a logo `<img>` tag to the report header introduces two print layout risks:
+
+1. **Logo too large:** An `<img>` without explicit CSS constraints stretches to its natural pixel size. A 1200×400 px banner image pushes the stats cards and table off the first page, breaking the expected report layout.
+2. **Image not printed:** Some users open HTML reports and use "Print to PDF." Browsers' print stylesheets apply `@media print` rules. By default, most browsers print background images but not inline `<img>` elements with `display:none` — this is usually not a problem, but logos inside `<div>` containers with `overflow:hidden` or certain CSS transforms may be clipped or omitted in print rendering.
+
+**Why it happens:**
+Logo sizing is set by the designer in the settings UI but the reports are opened in diverse browsers (Chrome, Edge, Firefox) with varying print margin defaults. The logo is tested visually on-screen but not in a print preview.
+
+**Prevention:**
+- Constrain all logo `<img>` elements with explicit CSS: `max-height: 60px; max-width: 200px; object-fit: contain;`. This prevents the image from overflowing its container regardless of the original image dimensions.
+- Add a `@media print` block in the report's inline CSS that keeps the logo visible and appropriately sized: `@media print { .report-logo { max-height: 48px; max-width: 160px; } }`.
+- Use `break-inside: avoid` on the header `<div>` containing both logos and the report title so a page break never splits the header from the first stat card.
+- Test "Print to PDF" in Edge (Chromium) before shipping — it is the most common browser for MSP tools on Windows.
+
+**Detection:**
+- Open a generated report in Edge, use Ctrl+P, check print preview. Verify the logo appears on page 1 and the table is not pushed to page 2 by an oversized image.
+
+**Phase to address:** HTML report template phase when logo injection is added to `BuildHtml`.
+
+---
+
+### Pitfall v2.2-8: ConsistencyLevel Header Amplifies Graph Throttling for Directory Listing
+
+**What goes wrong:**
+The existing `GraphUserSearchService` already uses `ConsistencyLevel: eventual` with `$count=true` for its `startsWith` filter query. This is required for the advanced filter syntax. However, applying `ConsistencyLevel: eventual` to a full directory listing with `$top=999` and `$orderby=displayName` forces Graph to route requests through a consistency-checked path rather than a lightweight read cache. Microsoft documentation confirms this increases the cost of each request against throttling limits.
+
+For a tenant with 10 000 users (11 pages of 999), firing 11 consecutive requests with `ConsistencyLevel: eventual` is significantly more expensive than 11 standard read requests. Under sustained MSP use (multiple tenants audited back-to-back), this can trigger per-app throttling (HTTP 429) after 2–3 directory loads in quick succession.
+
+**Why it happens:**
+`ConsistencyLevel: eventual` is already in the existing service and developers copy it to the new `GetAllUsersAsync` method because it was needed for `$count` support.
+
+**Prevention:**
+For `GetAllUsersAsync`, evaluate whether `ConsistencyLevel: eventual` is actually needed:
+- `$orderby=displayName` on `/users` does **not** require `ConsistencyLevel: eventual` — standard `$orderby` on `displayName` is supported without it.
+- `$count=true` does require `ConsistencyLevel: eventual`. If user count is needed for progress feedback, request it only on the first page, then use the returned `@odata.count` value without adding the header to subsequent page requests. The `PageIterator` does not automatically carry the header to next-link requests — verify this behaviour.
+- If `ConsistencyLevel: eventual` is not needed for the primary listing, omit it from `GetAllUsersAsync`. Use it only when `$search` or `$count` are required.
+
+**Detection:**
+- Load the full directory for two different tenants back-to-back. Check for HTTP 429 responses in the Serilog output. If throttling occurs within the first two loads, `ConsistencyLevel` overhead is the likely cause.
+
+**Phase to address:** User directory browse service implementation phase.
+
+---
+
+### Pitfall v2.2-9: WPF ListView with 5 000+ Users Freezes Without UI Virtualization
+
+**What goes wrong:**
+A WPF `ListView` or `DataGrid` bound to an `ObservableCollection<DirectoryUser>` with 5 000 items renders all 5 000 item containers on first bind if UI virtualization is disabled or inadvertently defeated. This causes a 5–10 second freeze when the directory loads and ~200 MB of additional memory for the rendered rows, even though only ~20 rows are visible in the viewport.
+
+Virtualization is defeated by any of these common mistakes:
+- The `ListView` is inside a `ScrollViewer` that wraps both the list and other content (`ScrollViewer.CanContentScroll=False` is the kill switch).
+- The `ItemsPanel` is overridden with a non-virtualizing panel (`StackPanel` instead of `VirtualizingStackPanel`).
+- Items are added one-by-one to the `ObservableCollection` (each addition fires a `CollectionChanged` notification, causing incremental layout passes — 5 000 separate layout passes are expensive).
+
+**Why it happens:**
+The existing people-picker `SearchResults` collection has at most 10 items — virtualization was never needed and its absence was never noticed. The directory browse `ObservableCollection` is a different scale.
+
+**Prevention:**
+- Use a `ListView` with its default `VirtualizingStackPanel` (do not override `ItemsPanel`).
+- Set `VirtualizingPanel.IsVirtualizing="True"`, `VirtualizingPanel.VirtualizationMode="Recycling"`, and `ScrollViewer.CanContentScroll="True"` explicitly — do not rely on defaults being correct after a XAML edit.
+- Never add items to the collection one-by-one from the background thread. Use `BindingOperations.EnableCollectionSynchronization` and assign `new ObservableCollection<T>(loadedList)` in one operation after all pages have been fetched, or batch-swap when each page arrives.
+- For 5 000+ items, add a search-filter input above the directory list that filters the bound `ICollectionView` — this reduces the rendered item count to a navigable size without requiring the user to scroll 5 000 rows.
+
+**Detection:**
+- Load a 3 000-user directory into the ListView. Open Windows Task Manager. The WPF process should not spike above 300 MB during list rendering. Scroll should be smooth (60 fps) with recycling enabled.
+
+**Phase to address:** User directory browse View/XAML phase.
+
+---
+
+### Pitfall v2.2-10: Dual Logo Injection Requires Coordinated Changes Across All Five HTML Export Services
+
+**What goes wrong:**
+There are five independent `HtmlExportService`-style classes, each with its own `BuildHtml` method that builds the full HTML document from scratch using `StringBuilder`. Adding logo support means changing all five methods. If logos are added to only two or three services (the ones the developer remembers), the other reports ship without branding. The inconsistency is subtle — the tool "works," but branded exports alternate with unbranded exports depending on which tab generated the report.
+
+**Why it happens:**
+Each export service was written independently and shares no base class. There is no shared "HTML report header" component that all services delegate to. Each service owns its complete `<!DOCTYPE html>` block.
+
+**Consequences:**
+- Permissions report is branded; duplicates report is not.
+- Client notices inconsistency and questions the tool's reliability.
+- Future changes to the report header (adding a timestamp, changing the color scheme) must be applied to all five files separately.
+
+**Prevention:**
+Before adding logo injection to any service, extract a shared `HtmlReportHeader` helper method (or a small `HtmlReportBuilder` base class/utility) that generates the `<head>`, `<style>`, and branded header `<div>` consistently. All five services call this shared method with a `BrandingOptions` parameter (MSP logo base64, client logo base64, report title). This is a refactoring prerequisite — not optional if branding consistency is required.
+
+The refactoring is low-risk: the CSS blocks in all five services are nearly identical (confirmed by reading the code), so consolidation is straightforward.
+
+**Detection:**
+- After branding is implemented, export one report from each of the five export services. Open all five in a browser side by side and verify logos appear in all five.
+
+**Phase to address:** HTML report template refactoring phase — this must be done before logo injection, not after.
+
+---
+
+## Minor Pitfalls (v2.2)
+
+### Pitfall v2.2-11: `User.Read.All` Permission Scope May Not Be Granted for Full Directory Listing
+
+**What goes wrong:**
+The existing `SearchUsersAsync` uses `startsWith` filter queries that work with `User.ReadBasic.All` (the least-privileged scope for user listing). Full directory browse with all user properties may require `User.Read.All`, depending on which properties are selected. If the Azure AD app registration used by MSP clients only has `User.ReadBasic.All` consented (which is sufficient for the v1.1 people-picker), the `GetAllUsersAsync` call may silently return partial data or throw a 403.
+
+`User.ReadBasic.All` returns only: `displayName`, `givenName`, `id`, `mail`, `photo`, `securityIdentifier`, `surname`, `userPrincipalName`. Requesting `accountEnabled` or `userType` (needed for filtering out guests/disabled accounts per Pitfall v2.2-3) requires `User.Read.All`.
+
+**Prevention:**
+- Define the exact `$select` fields needed for the directory browse feature and verify each field is accessible under `User.ReadBasic.All` before assuming `User.Read.All` is required.
+- If `User.Read.All` is required, update the app registration documentation and display a clear message in the tool if the required permission is missing (catch the 403 and surface it as "Insufficient permissions — User.Read.All is required for directory browse mode").
+- Add `User.Read.All` to the requested scopes in `MsalClientFactory` alongside existing scopes.
+
+**Detection:**
+- Test the directory browse against a tenant where the app registration has only `User.ReadBasic.All` consented. Verify the error message is user-readable, not a raw `ServiceException`.
+
+**Phase to address:** User directory browse service interface phase.
+
+---
+
+### Pitfall v2.2-12: Logo Preview in Settings UI Holds a File Lock
+
+**What goes wrong:**
+When showing a logo preview in the WPF settings UI using `BitmapImage` with a file URI (`new BitmapImage(new Uri(filePath))`), WPF may hold a read lock on the file until the `BitmapImage` is garbage collected. If the user then tries to re-import a different logo (which involves overwriting the same file), the file write fails with a sharing violation. This is a known WPF `BitmapImage` quirk.
+
+**Prevention:**
+Load logo previews with `BitmapCacheOption.OnLoad` and set `UriSource` then call `EndInit()`:
+```csharp
+var bitmap = new BitmapImage();
+bitmap.BeginInit();
+bitmap.UriSource = new Uri(filePath);
+bitmap.CacheOption = BitmapCacheOption.OnLoad;
+bitmap.EndInit();
+bitmap.Freeze(); // Makes it immutable and thread-safe; also releases the file handle
+```
+`Freeze()` is the critical call — it forces the image to be fully decoded into memory and releases the file handle immediately, preventing file locks.
+
+**Detection:**
+- Import a logo, then immediately try to overwrite the source file using Windows Explorer. Without `Freeze()`, the file is locked. With `Freeze()`, the overwrite succeeds.
+
+**Phase to address:** Settings UI / logo import phase.
+
+---
+
+## Phase-Specific Warnings (v2.2)
+
+| Phase Topic | Likely Pitfall | Mitigation |
+|-------------|---------------|------------|
+| Logo import + settings persistence | Base64 bloat (v2.2-1) + path staleness (v2.2-6) | Store pre-encoded base64 in JSON; enforce 512 KB import limit |
+| Logo import + settings persistence | Invalid/corrupt image file (v2.2-5) | Validate via `BitmapImage` load before persisting; `Freeze()` to release handle (v2.2-12) |
+| HTML report template refactoring | Inconsistent branding across 5 services (v2.2-10) | Extract shared header builder before touching any service |
+| HTML report template | Print layout broken by oversized logo (v2.2-7) | Add `max-height/max-width` CSS and `@media print` block |
+| Graph directory service | Silent truncation at 999 users (v2.2-2) | Use `PageIterator`; request `$count` on first page for progress |
+| Graph directory service | Guest/service account noise (v2.2-3) | Default filter `accountEnabled eq true and userType eq 'Member'`; UI toggle for guests |
+| Graph directory service | Throttling from ConsistencyLevel header (v2.2-8) | Omit `ConsistencyLevel: eventual` from standard listing; use only when `$search` or `$count` required |
+| Graph directory service | Missing permission scope (v2.2-11) | Verify `User.Read.All` vs. `User.ReadBasic.All` against required fields; update app registration docs |
+| Directory browse ViewModel | UI freeze during load (v2.2-4) | Stream pages via `IProgress<int>`; cancellable `AsyncRelayCommand` |
+| Directory browse View (XAML) | ListView freeze with 5 000+ items (v2.2-9) | Explicit virtualization settings; batch `ObservableCollection` assignment; filter input |
+
+---
+
+## v2.2 Integration Gotchas
+
+| Integration | Common Mistake | Correct Approach |
+|-------------|----------------|------------------|
+| Logo base64 in `AppSettings` JSON | Store file path; re-encode on every export | Store pre-encoded base64 string at import time; inject directly into `<img src>` |
+| `BitmapImage` logo preview | Default `BitmapImage` constructor holds file lock | Use `BeginInit/EndInit` with `BitmapCacheOption.OnLoad` and call `Freeze()` |
+| Graph `GetAllUsersAsync` | Single `GetAsync` call; no pagination | Always use `PageIterator<User, UserCollectionResponse>` |
+| Graph `$top` parameter | `$top=1000` — invalid; silently rounds down | Maximum valid value is `999` |
+| Graph directory filter | No filter — returns all account types | Default: `accountEnabled eq true and userType eq 'Member'` |
+| `ConsistencyLevel: eventual` | Applied to all Graph requests by habit | Required only for `$search`, `$filter` with non-standard operators, and `$count` |
+| HTML export services | Logo injected in only the modified services | Extract shared header builder; all five services use it |
+| WPF ListView with large user list | No virtualization settings, items added one-by-one | Explicit `VirtualizingPanel` settings; assign `new ObservableCollection<T>(list)` once |
+
+---
+
+## v2.2 "Looks Done But Isn't" Checklist
+
+- [ ] **Logo size limit enforced:** Import a 600 KB PNG. Verify the UI rejects it with a clear message and does not silently accept it.
+- [ ] **Corrupt image rejected:** Rename a `.txt` file to `.png` and attempt to import. Verify rejection with user-friendly error.
+- [ ] **Logo portability:** Import a logo on machine A, copy the settings JSON to machine B (without the original file), generate a report. Verify the logo appears.
+- [ ] **All five report types branded:** Export one report from each of the five HTML export services. Open all five in a browser and verify logos appear in all.
+- [ ] **Print layout intact:** Open each branded report type in Edge, Ctrl+P, print preview. Verify logo appears on page 1 and table is not displaced.
+- [ ] **Directory listing complete (large tenant):** Connect to a tenant with > 1 000 users. Load the full directory. Verify user count matches the Azure AD count shown in the Azure portal.
+- [ ] **Directory load cancellation:** Start a directory load and click Cancel before it completes. Verify the list shows partial results or is cleared, no crash, and the button re-enables.
+- [ ] **Guest account filter:** Verify guests are excluded by default. Verify the "Include guests" toggle adds them back.
+- [ ] **ListView performance:** Load 3 000 users into the directory list. Verify scroll is smooth and memory use is reasonable (< 400 MB total).
+- [ ] **FR locale for new UI strings:** All logo import labels, error messages, and directory browse UI strings must have FR translations. Verify no untranslated keys appear when FR is active.
+
+---
+
+## v2.2 Sources
+
+- Microsoft Learn: List users (Graph v1.0) — https://learn.microsoft.com/en-us/graph/api/user-list?view=graph-rest-1.0
+- Microsoft Learn: Graph API throttling guidance — https://learn.microsoft.com/en-us/graph/throttling
+- Microsoft Learn: Graph API service-specific throttling limits — https://learn.microsoft.com/en-us/graph/throttling-limits
+- Microsoft Learn: Graph SDK paging / PageIterator — https://learn.microsoft.com/en-us/graph/sdks/paging
+- Microsoft Learn: Graph permissions — User.ReadBasic.All vs User.Read.All — https://learn.microsoft.com/en-us/graph/permissions-reference
+- Rick Strahl's Web Log: Working around the WPF ImageSource Blues (2024) — https://weblog.west-wind.com/posts/2024/Jan/03/Working-around-the-WPF-ImageSource-Blues
+- Rick Strahl's Web Log: HTML to PDF Generation using the WebView2 Control (2024) — https://weblog.west-wind.com/posts/2024/Mar/26/Html-to-PDF-Generation-using-the-WebView2-Control
+- MDN Web Docs: CSS Printing — https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_media_queries/Printing
+- Microsoft Learn: BitmapImage / BitmapCacheOption — https://learn.microsoft.com/en-us/dotnet/api/system.windows.media.imaging.bitmapcacheoption
+- Microsoft Learn: Optimize WPF control performance (virtualization) — https://learn.microsoft.com/en-us/dotnet/desktop/wpf/advanced/optimizing-performance-controls
+- Microsoft Q&A: WPF BitmapImage complains about EXIF corrupt metadata — https://learn.microsoft.com/en-us/answers/questions/1457132/wpf-bitmapimage-complains-about-exif-corrupt-metad
+- Microsoft Q&A: What is the suggested way for filtering non-human accounts from /users — https://learn.microsoft.com/en-us/answers/questions/280526/what-is-the-suggested-34way34-or-best-options-for.html
+- DebugBear: Page Speed — Avoid Large Base64 data URLs — https://www.debugbear.com/blog/base64-data-urls-html-css
+- Graph API — how to avoid throttling (Tech Community) — https://techcommunity.microsoft.com/blog/fasttrackforazureblog/graph-api-integration-for-saas-developers/4038603
+- Existing codebase: `UserAccessHtmlExportService.cs`, `HtmlExportService.cs`, `GraphUserSearchService.cs` (reviewed 2026-04-08)
+
+---
+
+*v2.2 pitfalls appended: 2026-04-08*
@@ -1,204 +1,275 @@
-# Stack Research
+# Technology Stack

-**Domain:** C#/WPF desktop administration tool for SharePoint Online (multi-tenant MSP)
-**Researched:** 2026-04-02
-**Confidence:** HIGH (core framework choices), MEDIUM (charting library)
+**Project:** SharePoint Toolbox v2
+**Researched:** 2026-04-08 (updated for v2.2 milestone)

 ---

-## Recommended Stack
+## v2.2 Stack Additions

-### Core Technologies
-
-| Technology | Version | Purpose | Why Recommended |
-|------------|---------|---------|-----------------|
-| .NET 10 LTS | 10.x | Target runtime | Released November 2025, LTS until November 2028 — the current LTS. Avoid .NET 8 (ends November 2026) and .NET 9 STS (ended May 2026). WPF support is first-class and actively improved in .NET 10. |
-| WPF (.NET 10) | built-in | UI framework | Windows-only per project constraint. Modern MVVM data binding, richer styling than WinForms. The existing codebase uses WinForms; WPF is the correct upgrade path for richer UI. |
-| C# 13 | built-in with .NET 10 | Language | Current language version shipping with .NET 10 SDK. |
-
-### SharePoint / Microsoft 365 API
-
-| Library | Version | Purpose | Why Recommended |
-|---------|---------|---------|-----------------|
-| PnP.Framework | 1.18.0 | SharePoint CSOM extensions, provisioning engine, site templates, permissions | Directly replaces PnP.PowerShell patterns the existing app uses. Contains PnP Provisioning Engine needed for site templates feature. Targets .NET Standard 2.0 so runs on .NET 10 via compatibility. This is the correct choice for a CSOM-heavy migration — use PnP.Core SDK only when starting greenfield with Graph-first design. |
-| Microsoft.Graph | 5.103.0 | Microsoft Graph API access (Teams, Groups, users across tenants) | Required for Teams site management, user enumeration across tenants. Complements PnP.Framework which is CSOM-first. Use Graph SDK for Graph-native operations; use PnP.Framework for SharePoint-specific provisioning. |
-
-**Note on PnP.Core SDK vs PnP.Framework:** PnP Core SDK is the modern Graph-first replacement for PnP Framework, but PnP Framework is the right choice here because: (1) this is a migration from PnP.PowerShell which is CSOM-based, (2) the PnP Provisioning Engine for site templates lives in PnP.Framework, not PnP Core SDK, (3) the existing feature set maps directly to PnP.Framework's extension methods.
-
-### Authentication
-
-| Library | Version | Purpose | Why Recommended |
-|---------|---------|---------|-----------------|
-| Microsoft.Identity.Client (MSAL.NET) | 4.83.1 | Azure AD interactive browser login, token acquisition | The underlying auth library used by both PnP.Framework and Microsoft.Graph SDK. Use directly for multi-tenant session management. |
-| Microsoft.Identity.Client.Extensions.Msal | 4.83.3 | Token cache persistence to disk | Required for multi-tenant session caching — serializes the MSAL token cache to encrypted local storage so users don't re-authenticate on each app launch or tenant switch. PnP.Framework 1.18.0 already depends on this (>= 4.70.2). |
-| Microsoft.Identity.Client.Desktop | 4.82.1 | Windows-native broker support (WAM) | Enables Windows Authentication Manager integration for WPF apps. Provides system-level SSO. Add `.WithWindowsBroker()` to the PublicClientApplicationBuilder. |
-
-**Multi-tenant session caching pattern:** Create one `PublicClientApplication` per tenant, serialize each tenant's token cache separately using `MsalCacheHelper` from Extensions.Msal. Store serialized caches in `%AppData%\SharepointToolbox\tokens\{tenantId}.bin`. PnP.Framework's `AuthenticationManager.CreateWithInteractiveLogin()` accepts a custom MSAL app instance — wire the cached app here.
-
-### MVVM Infrastructure
-
-| Library | Version | Purpose | Why Recommended |
-|---------|---------|---------|-----------------|
-| CommunityToolkit.Mvvm | 8.4.2 | MVVM base classes, source-generated commands and properties, messaging | Microsoft-maintained, ships with .NET Community Toolkit. Source generators eliminate 90% of MVVM boilerplate. `[ObservableProperty]`, `[RelayCommand]`, `[INotifyPropertyChanged]` attributes generate all property change plumbing at compile time. The standard choice for WPF/MVVM in 2025-2026. |
-| Microsoft.Extensions.Hosting | 10.x | Generic Host for DI, configuration, lifetime management | Provides `IServiceCollection` DI container, `IConfiguration`, and structured app startup/shutdown lifecycle in WPF. Avoids manual service locator patterns. Wire WPF `Application.Startup` into the host lifetime. |
-| Microsoft.Extensions.DependencyInjection | 10.x | DI container | Included with Hosting. Register ViewModels, services, and repositories as scoped/singleton/transient services. |
-
-### Logging
-
-| Library | Version | Purpose | Why Recommended |
-|---------|---------|---------|-----------------|
-| Serilog | 4.3.1 | Structured logging | Industry standard for .NET desktop apps. Structured log events (not just strings) make post-mortem debugging of the existing app's 38 silent catch blocks tractable. File sink for persistent logs, debug sink for development. |
-| Serilog.Extensions.Logging | 10.0.0 | Bridge Serilog into ILogger<T> | Allows injecting `ILogger<T>` everywhere while Serilog handles the actual output. One configuration point. |
-| Serilog.Sinks.File | latest | Write logs to rolling files | `%AppData%\SharepointToolbox\logs\log-.txt` with daily rolling. Essential for diagnosing auth and SharePoint API failures in the field. |
-
-### Data Serialization
-
-| Library | Version | Purpose | Why Recommended |
-|---------|---------|---------|-----------------|
-| System.Text.Json | built-in .NET 10 | JSON read/write for profiles, settings, templates | Built into .NET, no NuGet dependency, faster and less memory-hungry than Newtonsoft.Json. Sufficient for the simple config/profile/template structures this app needs. The existing PowerShell app uses JSON — `System.Text.Json` with source generators enables AOT-safe deserialization, important for self-contained EXE size. |
-
-**Why not Newtonsoft.Json:** Slower, adds ~500KB to the EXE, no AOT support. Only justified when you need LINQ-to-JSON or highly polymorphic deserialization — neither of which applies here.
-
-### Data Visualization (Charts)
-
-| Library | Version | Purpose | Why Recommended |
-|---------|---------|---------|-----------------|
-| ScottPlot.WPF | 5.1.57 | Pie and bar charts for storage metrics | Stable, actively maintained (weekly releases), MIT licensed, no paid tier. Supports pie, bar, and all chart types needed. Renders via SkiaSharp — fast even for large datasets. LiveCharts2 is still RC for WPF (2.0.0-rc6.1 as of April 2026) and introduces unnecessary risk. OxyPlot is mature but lacks interactive features and has poor performance on large datasets. ScottPlot 5.x is the stable choice. |
-
-### Report Generation
-
-| Library | Version | Purpose | Why Recommended |
-|---------|---------|---------|-----------------|
-| CsvHelper | latest stable | CSV export | Industry standard for .NET CSV serialization. Handles encoding, quoting, header generation. Replaces manual string concatenation. |
-| No HTML library needed | — | HTML reports | Generate HTML reports via `StringBuilder` or T4/Scriban text templates with embedded JS (Chart.js or DataTables). Self-contained HTML files require no server. Keep it simple — a `ReportBuilder` service class is sufficient. |
-
-### Localization
-
-| Library | Version | Purpose | Why Recommended |
-|---------|---------|---------|-----------------|
-| .NET Resource files (.resx) | built-in | EN/FR localization | ResX is the standard WPF localization approach for a two-language desktop app. Compile-time safety, strong tooling in Visual Studio, no runtime switching complexity. The existing app uses a key-based translation system — ResX maps directly. Use `Properties/Resources.en.resx` and `Properties/Resources.fr.resx`. Runtime language switching (if needed later) is achievable via `Thread.CurrentThread.CurrentUICulture`. |
-
-### Distribution
-
-| Tool | Version | Purpose | Why Recommended |
-|------|---------|---------|-----------------|
-| `dotnet publish` with PublishSingleFile + SelfContained | .NET 10 SDK | Single self-contained EXE | Built-in SDK feature. Set `<PublishSingleFile>true</PublishSingleFile>`, `<SelfContained>true</SelfContained>`, `<RuntimeIdentifier>win-x64</RuntimeIdentifier>`. No third-party tool needed. Expected output size: ~150-200MB (runtime + SkiaSharp from ScottPlot). |
+This section covers only the NEW capability needs for v2.2 (Report Branding + User Directory). The full existing stack is documented in the section below. The short answer: **no new NuGet packages are needed for either feature.**

 ---

-## Project File Configuration
+### Feature 1: HTML Report Branding (Logo Embedding)

-```xml
-<PropertyGroup>
-  <TargetFramework>net10.0-windows</TargetFramework>
-  <UseWPF>true</UseWPF>
-  <Nullable>enable</Nullable>
-  <ImplicitUsings>enable</ImplicitUsings>
-  <!-- Distribution -->
-  <PublishSingleFile>true</PublishSingleFile>
-  <SelfContained>true</SelfContained>
-  <RuntimeIdentifier>win-x64</RuntimeIdentifier>
-  <!-- Trim carefully — MSAL and PnP use reflection -->
-  <PublishTrimmed>false</PublishTrimmed>
-</PropertyGroup>
+**Requirement:** Embed MSP logo (global) and client logo (per-tenant) into the self-contained HTML reports that already exist.
+
+#### Approach: Base64 data URI — BCL only
+
+The existing HTML export services (`HtmlExportService`, `UserAccessHtmlExportService`, etc.) produce fully self-contained HTML files using `StringBuilder` with all CSS and JS inlined. Logo images follow the same pattern: convert image bytes to a Base64 string and embed as an HTML `<img>` data URI.
+
+```csharp
+// In a LogoEmbedHelper or directly in each export service:
+byte[] bytes = await File.ReadAllBytesAsync(logoFilePath, ct);
+string mime  = Path.GetExtension(logoFilePath).ToLowerInvariant() switch
+{
+    ".png"  => "image/png",
+    ".jpg"  => "image/jpeg",
+    ".jpeg" => "image/jpeg",
+    ".gif"  => "image/gif",
+    ".svg"  => "image/svg+xml",
+    ".webp" => "image/webp",
+    _       => "image/png"
+};
+string dataUri = $"data:{mime};base64,{Convert.ToBase64String(bytes)}";
+// In HTML: <img src="{dataUri}" alt="Logo" style="height:48px;" />
 ```

-**Note on trimming:** Do NOT enable `PublishTrimmed` with PnP.Framework or MSAL.NET. Both libraries use reflection internally and are not trim-safe. The EXE will be larger (~150-200MB) but reliable. Trimming would require extensive `[DynamicDependency]` annotations and is not worth the effort.
+**Why this approach:**
+- Zero new dependencies. `File.ReadAllBytesAsync`, `Convert.ToBase64String`, and `Path.GetExtension` are all BCL.
+- The existing "no external dependencies" constraint on HTML reports is preserved.
+- Self-contained EXE constraint is preserved — no logo file paths can break because the bytes are embedded in the HTML at export time.
+- Base64 increases image size by ~33% but logos are small (< 50 KB typical); the impact on HTML file size is negligible.

---
+**Logo storage strategy — store file path, embed at export time:**

-## Installation (NuGet Package References)
+Store the logo file path (not the base64) in `AppSettings` (global MSP logo) and `TenantProfile` (per-client logo). At export time, the export service reads the file and embeds it. This keeps JSON settings files small and lets the user swap logos without re-entering settings.

-```xml
-<!-- SharePoint / Graph API -->
-<PackageReference Include="PnP.Framework" Version="1.18.0" />
-<PackageReference Include="Microsoft.Graph" Version="5.103.0" />
+- `AppSettings.MspLogoPath: string?` — path to MSP logo file
+- `TenantProfile.ClientLogoPath: string?` — path to client logo file for this tenant

-<!-- Authentication -->
-<PackageReference Include="Microsoft.Identity.Client" Version="4.83.1" />
-<PackageReference Include="Microsoft.Identity.Client.Extensions.Msal" Version="4.83.3" />
-<PackageReference Include="Microsoft.Identity.Client.Desktop" Version="4.82.1" />
+The settings UI uses WPF `OpenFileDialog` (already used in multiple ViewModels) to browse for image files — filter to `*.png;*.jpg;*.jpeg;*.gif;*.svg`.

-<!-- MVVM + DI -->
-<PackageReference Include="CommunityToolkit.Mvvm" Version="8.4.2" />
-<PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.0" />
+**Logo preview in WPF UI:** Use `BitmapImage` (built into `System.Windows.Media.Imaging`, already in scope for any WPF project). Bind a WPF `Image` control's `Source` to a `BitmapImage` loaded from the file path.

-<!-- Logging -->
-<PackageReference Include="Serilog" Version="4.3.1" />
-<PackageReference Include="Serilog.Extensions.Logging" Version="10.0.0" />
-<PackageReference Include="Serilog.Sinks.File" Version="5.0.0" />
+```csharp
+// In ViewModel — logo preview
+[ObservableProperty]
+private BitmapImage? _mspLogoPreview;

-<!-- Charts -->
-<PackageReference Include="ScottPlot.WPF" Version="5.1.57" />
-
-<!-- CSV Export -->
-<PackageReference Include="CsvHelper" Version="33.0.1" />
+partial void OnMspLogoPathChanged(string? value)
+{
+    if (string.IsNullOrWhiteSpace(value) || !File.Exists(value))
+    {
+        MspLogoPreview = null;
+        return;
+    }
+    var bmp = new BitmapImage();
+    bmp.BeginInit();
+    bmp.UriSource    = new Uri(value, UriKind.Absolute);
+    bmp.CacheOption  = BitmapCacheOption.OnLoad; // close file handle immediately
+    bmp.EndInit();
+    MspLogoPreview = bmp;
+}
 ```

---
-
-## Alternatives Considered
-
-| Category | Recommended | Alternative | Why Not |
-|----------|-------------|-------------|---------|
-| .NET version | .NET 10 LTS | .NET 8 LTS | .NET 8 support ends November 2026 — too soon for a new project to start on |
-| .NET version | .NET 10 LTS | .NET 9 STS | .NET 9 ended May 2026 — already past EOL at time of writing |
-| SharePoint API | PnP.Framework | PnP Core SDK | PnP Core SDK is Graph-first and not yet feature-complete for CSOM-heavy provisioning operations. Wrong choice for a migration from PnP.PowerShell patterns. |
-| MVVM toolkit | CommunityToolkit.Mvvm | Prism | Prism adds module/region/navigation complexity appropriate for large enterprise apps. This is a focused admin tool — CommunityToolkit.Mvvm is leaner and Microsoft-maintained. |
-| Charts | ScottPlot.WPF | LiveCharts2 | LiveCharts2 WPF package is still RC (2.0.0-rc6.1). Unstable API surface is inappropriate for production. |
-| Charts | ScottPlot.WPF | OxyPlot | OxyPlot has poor performance on large datasets and limited interactivity. Low activity/maintenance compared to ScottPlot 5. |
-| JSON | System.Text.Json | Newtonsoft.Json | Newtonsoft.Json adds ~500KB to EXE, is slower, and has no AOT support. Not needed for simple config structures. |
-| Localization | ResX (.resx files) | WPF ResourceDictionary XAML | ResourceDictionary localization is more complex, harder to maintain with tooling, and overkill for a two-language app. ResX provides compile-time safety. |
-| HTML reports | T4/StringBuilder | Razor / Blazor Hybrid | A dedicated template engine adds a dependency for what is a one-time file generation task. StringBuilder or Scriban (lightweight) is sufficient. |
-| Logging | Serilog | Microsoft.Extensions.Logging (built-in) | Built-in logging lacks file sinks and structured event support without additional providers. Serilog is de facto standard for desktop .NET apps. |
+**No new library needed:** `BitmapImage` lives in the WPF `PresentationCore` assembly, which is already a transitive dependency of any `<UseWPF>true</UseWPF>` project.

 ---

-## What NOT to Use
+### Feature 2: User Directory Browse Mode (Graph API)

-| Avoid | Why | Use Instead |
-|-------|-----|-------------|
-| LiveCharts2 WPF | Still in RC (2.0.0-rc6.1 as of April 2026) — unstable API, potential breaking changes before 2.0 GA | ScottPlot.WPF 5.1.57 (stable, weekly releases) |
-| PnP Core SDK (as primary SharePoint lib) | Graph-first design doesn't match the CSOM-heavy provisioning/permissions operations being migrated. The PnP Provisioning Engine is only in PnP.Framework | PnP.Framework 1.18.0 |
-| Prism Framework | Overengineered for this use case. Adds module system, region navigation complexity that doesn't match a single-window admin tool | CommunityToolkit.Mvvm 8.4.2 |
-| PublishTrimmed=true | PnP.Framework and MSAL.NET use reflection and are not trim-safe. Trimming causes runtime crashes | Keep trimming disabled; accept larger EXE |
-| .NET 8 as target | EOL November 2026 — a new project started now should not immediately be on a near-EOL runtime | .NET 10 LTS (supported until November 2028) |
-| SQLite / LiteDB | Out of scope per project constraints. JSON is sufficient for profiles, settings, templates. | System.Text.Json with file-based storage |
-| DeviceLogin / client secrets for auth | Per project memory note: MSP workflow requires interactive login, never DeviceLogin for PnP registration | MSAL interactive browser login via `WithInteractiveBrowser()` |
-| WinForms | The existing app is WinForms. The rewrite targets WPF explicitly for MVVM data binding and richer styling | WPF |
+**Requirement:** In the User Access Audit tab, add a "Browse" mode alternative to the people-picker search. Shows a paginated list of all users in the tenant — no search query, just the full directory — allowing the admin to pick users by scrolling/filtering locally.
+
+#### Graph API endpoint: GET /users (no filter)
+
+The existing `GraphUserSearchService` calls `GET /users?$filter=startsWith(...)` with `ConsistencyLevel: eventual`. Full directory listing removes the `$filter` and uses `$select` for the fields needed.
+
+**Minimum required fields for directory browse:**
+
+```
+displayName, userPrincipalName, mail, jobTitle, department, userType, accountEnabled
+```
+
+- `userType`: distinguish `"Member"` from `"Guest"` — useful for MSP admin context
+- `accountEnabled`: allow filtering out disabled accounts
+- `jobTitle` / `department`: helps admin identify the right user in large directories
+
+**Permissions required (confirmed from Microsoft Learn):**
+
+| Scope type | Minimum permission |
+|---|---|
+| Delegated (work/school) | `User.Read.All` |
+
+The existing auth uses `https://graph.microsoft.com/.default` which resolves to whatever scopes the Azure AD app registration has consented. If the MSP's app has `User.Read.All` consented (required for the existing people-picker to work), no new permission is needed — `GET /users` without `$filter` uses the same `User.Read.All` scope.
+
+**Pagination — PageIterator pattern:**
+
+`GET /users` returns a default page size of 100 with a maximum of 999 via `$top`. For tenants with hundreds or thousands of users, pagination via `@odata.nextLink` is mandatory.
+
+The `Microsoft.Graph` 5.x SDK (already installed at 5.74.0) includes `PageIterator<TEntity, TCollectionResponse>` in `Microsoft.Graph.Core`. No version upgrade required.
+
+```csharp
+// In a new IGraphUserDirectoryService / GraphUserDirectoryService:
+var firstPage = await graphClient.Users.GetAsync(config =>
+{
+    config.QueryParameters.Select = new[]
+    {
+        "displayName", "userPrincipalName", "mail",
+        "jobTitle", "department", "userType", "accountEnabled"
+    };
+    config.QueryParameters.Top   = 999; // max page size
+    config.QueryParameters.Orderby = new[] { "displayName" };
+    config.Headers.Add("ConsistencyLevel", "eventual");
+    config.QueryParameters.Count = true; // required for $orderby with eventual
+}, ct);
+
+var allUsers = new List<DirectoryUserResult>();
+
+var pageIterator = PageIterator<User, UserCollectionResponse>.CreatePageIterator(
+    graphClient,
+    firstPage,
+    user =>
+    {
+        if (user.AccountEnabled == true) // optionally skip disabled
+            allUsers.Add(new DirectoryUserResult(
+                user.DisplayName ?? user.UserPrincipalName ?? string.Empty,
+                user.UserPrincipalName ?? string.Empty,
+                user.Mail,
+                user.JobTitle,
+                user.Department,
+                user.UserType == "Guest"));
+        return true; // continue iteration
+    });
+
+await pageIterator.IterateAsync(ct);
+```
+
+**Why PageIterator over manual nextLink loop:**
+
+The Graph SDK's `PageIterator` correctly handles the `DirectoryPageTokenNotFoundException` pitfall — it uses the token from the last successful non-retry response for the next page request. Manual loops using `withUrl(nextLink)` are susceptible to this error if any retry occurs mid-iteration. The SDK pattern is the documented recommendation (Microsoft Learn, updated 2025-08-06).
+
+**Performance consideration — large tenants:**
+
+A tenant with 5,000 users fetching `$top=999` requires 5 API round-trips. At ~300-500 ms per call, this is 1.5–2.5 seconds total. This is acceptable for a browse-on-demand operation with a loading indicator. Do NOT load the directory automatically on tab open — require an explicit "Load Directory" button click.
+
+**Local filtering after load:**
+
+Once the full directory is in memory (as an `ObservableCollection<DirectoryUserResult>`), use `ICollectionView` with a `Filter` predicate for instant local text-filter — the same pattern already used in the `PermissionsViewModel` and `StorageViewModel`. No server round-trips needed for filtering once the list is loaded. This is already in-process for the existing ViewModels and requires no new library.
+
+**New model record:**
+
+```csharp
+// Core/Models/DirectoryUserResult.cs — or extend GraphUserResult
+public record DirectoryUserResult(
+    string DisplayName,
+    string UserPrincipalName,
+    string? Mail,
+    string? JobTitle,
+    string? Department,
+    bool IsGuest);
+```
+
+**New service interface:**
+
+```csharp
+// Services/IGraphUserDirectoryService.cs
+public interface IGraphUserDirectoryService
+{
+    Task<IReadOnlyList<DirectoryUserResult>> GetAllUsersAsync(
+        string clientId,
+        bool includeGuests = true,
+        bool includeDisabled = false,
+        CancellationToken ct = default);
+}
+```
+
+The implementation follows the same `GraphClientFactory` + `GraphServiceClient` pattern as `GraphUserSearchService`. Wire it in DI alongside the existing search service.

 ---

-## Version Compatibility Notes
+## No New NuGet Packages Required

-| Concern | Detail |
-|---------|--------|
-| PnP.Framework on .NET 10 | PnP.Framework targets .NET Standard 2.0, .NET 8.0, .NET 9.0. It runs on .NET 10 via .NET Standard 2.0 compatibility. No explicit .NET 10 TFM yet (as of April 2026), but the .NET Standard 2.0 path is stable. |
-| MSAL version pinning | PnP.Framework 1.18.0 requires `Microsoft.Identity.Client.Extensions.Msal >= 4.70.2`. Installing 4.83.3 satisfies this constraint. Pin to 4.83.x to avoid drift. |
-| Microsoft.Graph SDK major version | Use 5.x only. The 4.x to 5.x upgrade introduced Kiota-generated code with significant breaking changes. Do not mix 4.x and 5.x packages. |
-| CommunityToolkit.Mvvm source generators | 8.4.2 introduces partial properties support requiring C# 13 / .NET 9+ SDK. On .NET 10 this is fully supported. |
-| ScottPlot.WPF + SkiaSharp | ScottPlot 5.x bundles SkiaSharp. Ensure no version conflict if SkiaSharp is pulled in by another dependency. ScottPlot.WPF 5.1.57 bundles SkiaSharp 2.88.x. |
+| Feature | What's needed | How provided |
+|---|---|---|
+| Logo file → Base64 data URI | `Convert.ToBase64String`, `File.ReadAllBytesAsync` | BCL (.NET 10) |
+| Logo preview in WPF settings | `BitmapImage`, `Image` control | WPF / PresentationCore |
+| Logo file picker | `OpenFileDialog` | WPF / Microsoft.Win32 |
+| Store logo path in settings | `AppSettings.MspLogoPath`, `TenantProfile.ClientLogoPath` | Extend existing models |
+| User directory listing | `graphClient.Users.GetAsync()` + `PageIterator` | Microsoft.Graph 5.74.0 (already installed) |
+| Local filtering of directory list | `ICollectionView.Filter` | WPF / System.Windows.Data |
+
+**Do NOT add:**
+- Any HTML template engine (Razor, Scriban, Handlebars) — `StringBuilder` is sufficient for logo injection
+- Any image processing library (ImageSharp, SkiaSharp standalone, Magick.NET) — no image transformation is needed, only raw bytes → Base64
+- Any new Graph SDK packages — `Microsoft.Graph` 5.74.0 already includes `PageIterator`
+
+---
+
+## Impact on Existing Services
+
+### HTML Export Services
+
+Each existing export service (`HtmlExportService`, `UserAccessHtmlExportService`, `StorageHtmlExportService`, `DuplicatesHtmlExportService`, `SearchHtmlExportService`) needs a logo injection point. Two options:
+
+**Option A (recommended): `ReportBrandingContext` parameter**
+
+Introduce a small record carrying resolved logo data URIs. Export services accept it as an optional parameter; when null, no logo header is rendered. This keeps the services testable without file I/O.
+
+```csharp
+public record ReportBrandingContext(
+    string? MspLogoDataUri,    // "data:image/png;base64,..." or null
+    string? ClientLogoDataUri, // "data:image/png;base64,..." or null
+    string? MspName,
+    string? ClientName);
+```
+
+A `ReportBrandingService` converts file paths to data URIs. ViewModels call it before invoking the export service.
+
+**Option B: Inject branding directly into all BuildHtml signatures**
+
+Less clean — modifies every export service signature and every call site.
+
+Option A is preferred: it isolates file I/O from HTML generation and keeps existing tests passing without changes.
+
+### UserAccessAuditViewModel
+
+Add a `BrowseMode` boolean property (bound to a RadioButton or ToggleButton). When `true`, show the directory list panel instead of the people-picker search box. The `IGraphUserDirectoryService` is injected alongside the existing `IGraphUserSearchService`.
+
+---
+
+## Existing Stack (Unchanged)
+
+The full stack as validated through v1.1:
+
+| Technology | Version | Purpose |
+|---|---|---|
+| .NET 10 | 10.x | Target runtime (LTS until Nov 2028) |
+| WPF | built-in | UI framework |
+| C# 13 | built-in | Language |
+| PnP.Framework | 1.18.0 | SharePoint CSOM, provisioning engine |
+| Microsoft.Graph | 5.74.0 | Graph API (users, Teams, Groups) |
+| Microsoft.Identity.Client (MSAL) | 4.83.3 | Multi-tenant auth, token acquisition |
+| Microsoft.Identity.Client.Extensions.Msal | 4.83.3 | Token cache persistence |
+| Microsoft.Identity.Client.Broker | 4.82.1 | Windows broker (WAM) |
+| CommunityToolkit.Mvvm | 8.4.2 | MVVM base classes, source generators |
+| Microsoft.Extensions.Hosting | 10.0.0 | DI container, app lifetime |
+| LiveCharts2 (SkiaSharpView.WPF) | 2.0.0-rc5.4 | Storage charts (in use, stable enough) |
+| Serilog | 4.3.1 | Structured logging |
+| Serilog.Extensions.Hosting | 10.0.0 | ILogger<T> bridge |
+| Serilog.Sinks.File | 7.0.0 | Rolling file output |
+| CsvHelper | 33.1.0 | CSV export |
+| System.Text.Json | built-in | JSON settings/profiles/templates |
+| xUnit | 2.9.3 | Unit tests |
+| Moq | 4.20.72 | Test mocking |

 ---

 ## Sources

- NuGet: https://www.nuget.org/packages/PnP.Framework/ — version 1.18.0 confirmed, .NET targets confirmed
- NuGet: https://www.nuget.org/packages/Microsoft.Graph/ — version 5.103.0 confirmed
- NuGet: https://www.nuget.org/packages/microsoft.identity.client — version 4.83.1 confirmed
- NuGet: https://www.nuget.org/packages/Microsoft.Identity.Client.Extensions.Msal/ — version 4.83.3 confirmed
- NuGet: https://www.nuget.org/packages/CommunityToolkit.Mvvm/ — version 8.4.2 confirmed
- NuGet: https://www.nuget.org/packages/ScottPlot.WPF — version 5.1.57 (stable), 5.1.58 (latest as of March 2026)
- NuGet: https://www.nuget.org/packages/serilog/ — version 4.3.1 confirmed
- Microsoft Learn: https://learn.microsoft.com/en-us/dotnet/core/deploying/single-file/overview — PublishSingleFile guidance, .NET 8+ SelfContained behavior change
- .NET Blog: https://devblogs.microsoft.com/dotnet/announcing-dotnet-10/ — .NET 10 LTS November 2025 GA
- .NET Support Policy: https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core — LTS lifecycle dates
- PnP Framework GitHub: https://github.com/pnp/pnpframework — .NET targets, auth patterns
- PnP Framework vs Core comparison: https://github.com/pnp/pnpframework/issues/620 — authoritative guidance on which library to use
- MSAL token cache: https://learn.microsoft.com/en-us/entra/msal/dotnet/how-to/token-cache-serialization — cache serialization patterns
- CommunityToolkit 8.4 announcement: https://devblogs.microsoft.com/dotnet/announcing-the-dotnet-community-toolkit-840/ — partial properties, .NET 10 support
-
---
-
-*Stack research for: SharePoint Online administration desktop tool (C#/WPF)*
-*Researched: 2026-04-02*
+- Microsoft Learn — List users (Graph v1.0): https://learn.microsoft.com/en-us/graph/api/user-list?view=graph-rest-1.0 — permissions, $top max 999, $orderby with ConsistencyLevel, default fields (HIGH confidence, updated 2025-07-23)
+- Microsoft Learn — Page through a collection (Graph SDKs): https://learn.microsoft.com/en-us/graph/sdks/paging — PageIterator C# pattern, DirectoryPageTokenNotFoundException warning (HIGH confidence, updated 2025-08-06)
+- Microsoft Learn — Get organizationalBranding: https://learn.microsoft.com/en-us/graph/api/organizationalbranding-get?view=graph-rest-1.0 — branding stream retrieval via localizations/default/bannerLogo (HIGH confidence, updated 2025-11-08) — note: tenant branding pull is optional/future, not required for v2.2 which relies on user-supplied logo files
+- .NET Perls / BCL docs — Convert.ToBase64String + data URI pattern: confirmed BCL, no library needed (HIGH confidence)
+- Existing codebase inspection: GraphClientFactory.cs, GraphUserSearchService.cs, HtmlExportService.cs, UserAccessHtmlExportService.cs, TenantProfile.cs, AppSettings.cs — confirmed exact integration points
@@ -2,6 +2,349 @@

 **Project:** SharePoint Toolbox — C#/WPF SharePoint Online Administration Desktop Tool
 **Domain:** SharePoint Online administration, auditing, and provisioning (MSP / IT admin)
+**Researched:** 2026-04-02 (v1.0 original) | 2026-04-08 (v2.2 addendum)
+**Confidence:** HIGH
+
+---
+
+> **Note:** This file contains two sections. The original v1.0 research summary is preserved below
+> the v2.2 section. The roadmapper should consume **v2.2 first** for the current milestone.
+
+---
+
+# v2.2 Research Summary — Report Branding & User Directory
+
+**Milestone:** v2.2 — HTML Report Branding (MSP/client logos) + User Directory Browse Mode
+**Synthesized:** 2026-04-08
+**Sources:** STACK.md (v2.2 addendum), FEATURES.md (v2.2), ARCHITECTURE.md (v2.2), PITFALLS.md (v2.2 addendum)
+
+---
+
+## Executive Summary
+
+v2.2 adds two independent, self-contained features to a mature WPF MVVM codebase: logo branding
+across all five HTML export services, and a full-directory browse mode as an alternative to the
+existing people-picker in the User Access Audit tab. Both features are well within the capabilities
+of the existing stack — no new NuGet packages are required. The implementation path is low risk
+because neither feature touches the audit execution engine; they are purely additive layers on top
+of proven infrastructure.
+
+The branding feature follows a single clear pattern: store logos as base64 strings in existing JSON
+settings and profile files, pass them at export time via a new optional `ReportBranding` record, and
+inject `<img data-URI>` tags into a shared HTML header block. The architecture keeps the five export
+services independent (each receives an optional parameter) while avoiding code duplication through a
+shared header builder. The user directory browse feature adds a new `IGraphUserDirectoryService`
+alongside the existing search service, wires it to new ViewModel state in
+`UserAccessAuditViewModel`, and presents it as a toggle-panel in the View. The existing audit
+pipeline is completely untouched.
+
+The primary risks are not technical complexity but execution discipline: logo size must be enforced
+at import time (512 KB limit) to prevent HTML report bloat, Graph pagination must use `PageIterator`
+to handle tenants with more than 999 users, and logo data must be stored as base64 strings (not file
+paths) to ensure portability across machines. All three of these are straightforward to implement
+once the storage strategy is decided and locked in at the beginning of each feature's implementation
+phase.
+
+---
+
+## Key Findings
+
+### Stack Additions — None Required
+
+The entire v2.2 scope is served by the existing stack:
+
+| Capability | Provided By | Notes |
+|---|---|---|
+| Logo encoding (file → base64) | BCL `Convert.ToBase64String` + `File.ReadAllBytesAsync` | Zero new packages |
+| Logo preview in WPF settings UI | `BitmapImage` (WPF PresentationCore, already a transitive dep) | Standard WPF pattern |
+| Logo file picker | `OpenFileDialog` (WPF Microsoft.Win32, already used in codebase) | Filter to PNG/JPG/GIF/BMP |
+| User directory listing with pagination | `Microsoft.Graph` 5.74.0 `PageIterator<User, UserCollectionResponse>` | Already installed |
+| Local directory filtering | `ICollectionView.Filter` (WPF System.Windows.Data) | Already used in PermissionsViewModel |
+| Logo + profile JSON persistence | `System.Text.Json` + existing Repository pattern | Backward-compatible nullable fields |
+
+Do NOT add: HTML template engines (Razor/Scriban), image processing libraries (ImageSharp,
+Magick.NET), or PDF export libraries. All explicitly out of scope.
+
+---
+
+### Feature Table Stakes vs. Differentiators
+
+**Feature 1: HTML Report Branding**
+
+Table stakes (must ship):
+- MSP global logo in every HTML report header
+- Client (per-tenant) logo in report header
+- Logo renders without external URL (data-URI embedding for self-contained HTML portability)
+- Graceful absence — no broken image icon when logo is not configured
+- Consistent placement across all five HTML export types
+
+Differentiators (build after table stakes):
+- Auto-pull client logo from Microsoft Entra tenant branding (`GET /organization/{id}/branding/localizations/default/bannerLogo`) — zero-config path using the existing `User.Read` delegated scope
+- Report timestamp and tenant display name in header
+
+Anti-features — do not build:
+- Per-tenant CSS color themes (design system complexity, disproportionate to MSP value)
+- PDF export with embedded logo (requires third-party binary dependency)
+- SVG logo support (XSS risk in data-URIs; PNG/JPG/GIF/BMP only)
+- Hotlinked logo URL field (breaks offline/archived reports)
+
+**Feature 2: User Directory Browse Mode**
+
+Table stakes (must ship):
+- Full directory listing (all enabled member users) with pagination
+- In-memory text filter on DisplayName/UPN/Mail without server round-trips
+- Sortable columns (Name, UPN)
+- Select user from list to trigger existing audit pipeline
+- Loading indicator with user count feedback ("Loaded X users...")
+- Toggle between Browse mode and Search (people-picker) mode
+
+Differentiators (add after core browse is stable):
+- Filter by account type (member vs. guest toggle)
+- Department / Job Title columns
+- Session-scoped directory cache (invalidated on tenant switch)
+
+Anti-features — do not build:
+- Eager load on tab open (large tenants block UI and risk throttling)
+- Delta query / incremental sync (wrong pattern for single-session audit)
+- Multi-user bulk simultaneous audit (different results model, out of scope)
+- Export user directory to CSV (identity reporting, not access audit)
+
+**Recommended MVP build order:**
+1. MSP logo in all HTML reports — highest visible impact, lowest complexity
+2. Client logo in HTML reports (import from file) — completes co-branding
+3. User directory browse core (load, select, filter, pipe into audit)
+4. Auto-pull client logo from Entra branding — add after file import path is proven
+5. Directory guest filter + department/jobTitle columns — low-effort polish
+
+---
+
+### Architecture Integration Points and Build Order
+
+**New files to create (7):**
+
+| Component | Layer | Purpose |
+|---|---|---|
+| `Core/Models/BrandingSettings.cs` | Core/Models | MSP logo base64 + MIME type; global, persisted in `branding.json` |
+| `Core/Models/ReportBranding.cs` | Core/Models | Lightweight record assembled at export time; NOT persisted |
+| `Core/Models/PagedUserResult.cs` | Core/Models | Page of `GraphUserResult` items + next-page cursor token |
+| `Infrastructure/Persistence/BrandingRepository.cs` | Infrastructure | Atomic JSON write (mirrors SettingsRepository pattern exactly) |
+| `Services/BrandingService.cs` | Services | Orchestrates file read → MIME detect → base64 → save |
+| `Services/IGraphUserDirectoryService.cs` | Services | Contract for paginated tenant user enumeration |
+| `Services/GraphUserDirectoryService.cs` | Services | Graph API user listing with `PageIterator` cursor pagination |
+
+**Existing files to modify (17), by risk level:**
+
+Medium risk (left-panel restructure or new async command):
+- `ViewModels/Tabs/UserAccessAuditViewModel.cs` — add `IGraphUserDirectoryService` injection + browse mode state/commands
+- `Views/Tabs/UserAccessAuditView.xaml` — add mode toggle + browse panel in left column
+
+Low risk (optional param or uniform inject-and-call pattern, batchable):
+- All 5 `Services/Export/*HtmlExportService.cs` — add `ReportBranding? branding = null` optional parameter
+- `PermissionsViewModel`, `StorageViewModel`, `SearchViewModel`, `DuplicatesViewModel` — add `BrandingService` injection + use in `ExportHtmlAsync`
+- `SettingsViewModel.cs` — add MSP logo browse/preview/clear commands
+- `ProfileManagementViewModel.cs` — add client logo browse/preview/clear commands
+- `SettingsView.xaml`, `ProfileManagementDialog.xaml` — add logo UI sections
+- `App.xaml.cs` — register 3 new services
+
+**Dependency-aware build phases:**
+
+| Phase | Scope | Risk | Gate |
+|---|---|---|---|
+| A — Models | BrandingSettings, ReportBranding, PagedUserResult, TenantProfile logo fields | None | POCOs; no dependencies |
+| B — Services | BrandingRepository, BrandingService, IGraphUserDirectoryService, GraphUserDirectoryService | Low | Unit-testable with mocks; Phase A required |
+| C — Export services | Add optional `ReportBranding?` to all 5 HTML export services | Low | Phase A required; regression tests: null branding produces identical HTML |
+| D — Branding ViewModels | SettingsVM, ProfileManagementVM, 4 export VMs, App.xaml.cs registration | Low | Phase B+C required; steps are identical pattern, batch them |
+| E — Directory ViewModel | UserAccessAuditViewModel browse mode state + commands | Medium | Phase B required; do after branding ViewModel pattern is proven |
+| F — Branding Views | SettingsView.xaml, ProfileManagementDialog.xaml, base64→BitmapSource converter | Low | Phase D required; write converter once, reuse in both views |
+| G — Directory View | UserAccessAuditView.xaml + code-behind SelectionChanged handler | Medium | Phase E required; do last, after ViewModel unit tests pass |
+
+Key architectural constraints (must not violate):
+- **Client logo on `TenantProfile`, NOT in `BrandingSettings`.** Client logos are per-tenant; mixing them with global MSP settings makes per-profile deletion and serialization awkward.
+- **Logos stored as base64 strings in JSON, not as file paths.** File paths become stale when the tool is redistributed to another machine. Decided once at Phase A; all downstream phases depend on it.
+- **Export services use optional `ReportBranding?` parameter, not required.** All existing call sites compile unchanged; branding is injected only where desired.
+- **No `IHtmlExportService` interface for this change.** The existing 5-concrete-classes pattern needs no interface for an optional parameter addition.
+- **`GraphUserDirectoryService` is a new service, separate from `GraphUserSearchService`.** Different call patterns (no `startsWith` filter, different pagination), different cancellation needs.
+- **Do NOT load the directory automatically on tab open.** Require explicit "Load Directory" button click to avoid blocking UI on large tenants.
+
+---
+
+### Top Pitfalls and Prevention Strategies
+
+**v2.2-1 (Critical): Base64 logo bloat in every report**
+Large source images (300-600 KB originals) become 400-800 KB of base64 inlined in every exported
+HTML file, re-allocated on every export call.
+Prevention: Enforce 512 KB max at import time in the settings UI. Store pre-encoded base64 in JSON
+(computed once on import, never re-encoded). Inject the cached string directly into the `<img>` tag.
+
+**v2.2-2 (Critical): Graph directory listing silently truncates at 999 users**
+`GET /users` returns at most 999 per page. A 5,000-user tenant appears to have 999 users with no
+error and no indication of truncation.
+Prevention: Use `PageIterator<User, UserCollectionResponse>` for all full directory fetches. Never
+call `.GetAsync()` on the users collection without following `@odata.nextLink` until null.
+
+**v2.2-3 (Critical): Directory browse exposes guests, service accounts, and disabled accounts by default**
+Raw `GET /users` returns all object types. An MSP tenant with 50+ guest collaborators and service
+accounts produces a noisy, confusing directory.
+Prevention: Default filter `accountEnabled eq true and userType eq 'Member'`. Expose an "Include
+guest accounts" checkbox for explicit opt-in. Apply this filter at the service level, not the
+ViewModel, so the ViewModel is not aware of Graph filter syntax.
+
+**v2.2-4 (Critical): Directory load hangs UI without progress feedback**
+3,000-user tenant takes 3-8 seconds. Without count feedback, the user assumes the feature is
+broken and may double-click the button (triggering concurrent Graph requests).
+Prevention: `DirectoryLoadStatus` observable property updated via `IProgress<int>` in the
+PageIterator callback ("Loading... X users"). Guard `AsyncRelayCommand.CanExecute` during loading.
+Add cancellation button wired to the same `CancellationToken` passed to `PageIterator.IterateAsync`.
+
+**v2.2-5 (Critical): Logo file format validation skipped — broken images in reports**
+OpenFileDialog filter is not sufficient. Renamed non-image files, corrupted JPEGs, and SVG files
+pass the filter but produce broken `<img>` tags in generated reports.
+Prevention: Validate by loading as `BitmapImage` in a try/catch before persisting. Check
+`PixelWidth` and `PixelHeight` are non-zero. Use `BitmapCacheOption.OnLoad` + retry with
+`IgnoreColorProfile` for EXIF-corrupt JPEGs. Reject SVG explicitly.
+
+**v2.2-6 (Critical): Logo file path stored in JSON becomes stale across machines**
+Storing `C:\Users\admin\logos\msp-logo.png` works on the import machine only. After redistribution
+or reinstall, the path is missing and logos silently disappear from new reports.
+Prevention: Store base64 string directly in `AppSettings` and `TenantProfile` JSON. The original
+file path is discarded after import. The settings file becomes fully portable.
+
+**Moderate pitfalls:**
+- v2.2-7: Logo breaks HTML report print layout — apply `max-height: 60px; max-width: 200px` CSS and add `@media print` rules in the report `<style>` block.
+- v2.2-8: Logo cleared on profile overwrite — verify `ClientLogoBase64` and `ClientLogoMimeType` survive the profile save/reload cycle before shipping.
+- v2.2-9: `DirectoryPageTokenNotFoundException` on Graph page iteration retry — use `PageIterator` (which handles retry token correctly) rather than a manual `@odata.nextLink` loop.
+
+---
+
+## Implications for Roadmap
+
+### Suggested Phase Structure
+
+The two features are architecturally independent. A single developer should follow phases A-G in
+order. Two developers can run branding (A→D→F) and directory browse (A→B→E→G) in parallel after
+Phase A completes.
+
+**Phase 1 — Data foundation (models + repositories + services)**
+Rationale: Unblocks both features simultaneously. Establishes the logo storage strategy (base64-in-
+JSON) before any export service or ViewModel is written. Establishing this here prevents a full
+re-architecture later if file-path storage is chosen first.
+Delivers: Phases A + B from the build order above.
+Key decision to make before starting: confirm base64-in-JSON as the storage strategy (not file
+paths). Document the decision explicitly.
+Pitfalls to avoid: v2.2-6 (file path portability). The wrong storage decision here propagates to
+all downstream phases.
+
+**Phase 2 — HTML export service extensions + branding ViewModel integration**
+Rationale: Modifying the 5 export services with an optional parameter is low-risk and unblocks all
+ViewModel callers. The 4 export ViewModel changes are an identical inject-and-call pattern — batch
+them. The SettingsViewModel and ProfileManagementViewModel changes complete the logo management UX.
+Delivers: Phases C + D from the build order above. All HTML reports support optional logo headers.
+MSP logo manageable from Settings. Client logo manageable from ProfileManagementDialog.
+Pitfalls to avoid: v2.2-1 (size limit at import), v2.2-5 (file format validation), v2.2-7 (print
+layout CSS). All three must be implemented in this phase, not deferred.
+
+**Phase 3 — Branding UI views**
+Rationale: Views built after ViewModel behavior is unit-tested. Requires the base64→BitmapSource
+converter, written once and reused in both views.
+Delivers: Phase F from the build order. Settings branding section + ProfileManagementDialog logo
+fields, both with live preview.
+
+**Phase 4 — User directory browse ViewModel**
+Rationale: `UserAccessAuditViewModel` is the highest-risk change. New async command with progress,
+cancellation, and tenant-switch reset. Implement and unit-test before touching the View.
+Delivers: Phase E from the build order. Full browse mode behavior is testable via unit tests before
+any XAML is written.
+Pitfalls to avoid: v2.2-2 (pagination), v2.2-3 (default filter), v2.2-4 (progress feedback),
+v2.2-9 (PageIterator vs. manual nextLink loop).
+
+**Phase 5 — Directory browse UI view**
+Rationale: Left panel restructure in UserAccessAuditView.xaml is the highest-risk XAML change.
+Done last, after all ViewModel behavior is proven by tests.
+Delivers: Phase G from the build order. Complete browse mode UX.
+
+**Phase 6 — Differentiators (after core features proven)**
+Rationale: Auto-pull Entra branding, directory guest filter toggle, department/jobTitle columns,
+session-scoped directory cache. These are enhancements, not blockers for the milestone.
+Delivers: Zero-config client logo path, richer directory filtering, faster repeat access.
+Pitfalls to avoid: Auto-pull Entra logo must handle empty-body response gracefully (not all tenants
+have branding configured). Fall back silently to no logo rather than showing an error.
+
+### Research Flags
+
+Phases 1-5 are standard patterns verified by direct codebase inspection. No additional research
+needed. The architecture file provides exact file locations, class signatures, and data flows.
+
+Phase 6 (auto-pull Entra branding): MEDIUM confidence. Test the `bannerLogo` stream endpoint
+against a real tenant with and without branding configured before committing to the implementation.
+The Graph API documentation states the response is an empty stream (not a 404) when no logo is set
+— verify this behavior live before building the error handling path around it.
+
+---
+
+## Open Questions for Product Decisions
+
+These are not technical blockers but should be resolved before the phase that implements them:
+
+1. **SVG logo support: anti-feature or bring-your-own-library feature?**
+   Current recommendation: reject SVG (XSS risk in data-URIs, requires SharpVectors for rasterization). If SVG support is needed, SharpVectors adds a dependency. Decide before Phase 2.
+
+2. **Client logo source priority when both auto-pull and manual import are configured?**
+   Recommendation: manual import wins; auto-pull is the fallback when no manual logo is set.
+   Implement as `ClientLogoSource` enum: `None | Imported | AutoPulled`. Decide before Phase 6.
+
+3. **Session-scoped directory cache: ViewModel lifetime or shared service?**
+   ViewModel-scoped = cache lost on tab navigation (ViewModel is transient). Service-scoped = cache
+   survives tab switches. Recommendation: start with no cache (Refresh button), add service-level
+   caching in Phase 6 only if user feedback indicates it is needed. Defers scope decision.
+
+4. **Report header layout: logos side-by-side or MSP left + client right?**
+   Visual design decision only; does not affect services or ViewModels. Current spec uses
+   `display: flex; gap: 16px` (left-to-right). Can be changed at any time.
+
+5. **"Load Directory" button placement: inside browse panel or tab-level toolbar?**
+   Recommendation: inside the browse panel, visible only in Browse mode. Avoids confusion when in
+   Search mode. Does not affect architecture.
+
+---
+
+## Confidence Assessment (v2.2)
+
+| Area | Confidence | Basis |
+|---|---|---|
+| Stack (no new packages needed) | HIGH | Direct codebase inspection + BCL and Graph SDK documentation |
+| Feature scope (table stakes vs. differentiators) | HIGH | Official Graph API docs + direct codebase inspection + MSP tool competitive research |
+| Architecture (integration points, build order) | HIGH | Direct inspection of all affected files; exact class names and property signatures verified |
+| Branding pitfalls (base64, file validation, portability) | HIGH | BCL behavior verified; file path portability pitfall is a well-known pattern |
+| Graph pagination pitfalls | HIGH | Microsoft Learn PageIterator docs (updated 2025-08-06); DirectoryPageTokenNotFoundException documented |
+| Directory filter behavior (accountEnabled, userType) | MEDIUM-HIGH | Graph docs confirm filter syntax; recommend verifying against a real tenant before shipping |
+| Auto-pull Entra banner logo (Phase 6) | MEDIUM | API documented but empty-body behavior (no logo configured) needs live tenant verification |
+| Print CSS behavior for logo header | MEDIUM | MDN/W3C verified; browser rendering varies; requires cross-browser manual test |
+
+**Overall confidence:** HIGH for Phases 1-5. MEDIUM for Phase 6 (Entra auto-pull live behavior).
+
+**Gaps to address during planning:**
+- Confirm `$filter=accountEnabled eq true and userType eq 'Member'` works without `ConsistencyLevel: eventual` on the v1.0 `/users` endpoint. If eventual consistency is required, the `GraphUserDirectoryService` adds the `ConsistencyLevel` header and `$count=true` to this call path.
+- Verify the Entra `bannerLogo` stream endpoint returns an empty response body (not HTTP 404) when tenant branding is not configured. This determines the error handling branch in the auto-pull code path.
+
+---
+
+## Sources (v2.2)
+
+| Source | Confidence | Used In |
+|---|---|---|
+| Microsoft Learn — List users (Graph v1.0), updated 2025-07-23 | HIGH | STACK, FEATURES, PITFALLS |
+| Microsoft Learn — Page through a collection (Graph SDKs), updated 2025-08-06 | HIGH | STACK, PITFALLS |
+| Microsoft Learn — Get organizationalBranding (Graph v1.0), updated 2025-11-08 | HIGH | STACK, FEATURES |
+| .NET BCL docs — Convert.ToBase64String, File.ReadAllBytesAsync | HIGH | STACK |
+| Microsoft Learn — Graph throttling guidance | HIGH | PITFALLS |
+| Direct codebase inspection (GraphClientFactory, HtmlExportService, TenantProfile, AppSettings, UserAccessAuditViewModel, SettingsViewModel, UserAccessAuditView.xaml, App.xaml.cs) | HIGH | ARCHITECTURE, STACK |
+| Existing codebase CONCERNS.md audit (2026-04-02) | HIGH | PITFALLS |
+
+---
+---
+
+# v1.0 Research Summary (Original — Preserved for Reference)
+
 **Researched:** 2026-04-02
 **Confidence:** HIGH

@@ -50,7 +393,7 @@ The feature scope is well-researched. Competitive analysis against ShareGate, Ma
 **Should have (competitive differentiators — v1.x):**
 - User access export across selected sites — "everything User X can access across 15 sites" — no native M365 equivalent
 - Simplified permissions view (plain language) — "can edit files" instead of "Contribute"
- Storage graph by file type (pie + bar toggle) — file-type breakdown competitors don't provide
+- Storage graph by file type (pie + bar toggle) via ScottPlot.WPF

 **Defer (v2+):**
 - Scheduled scan runs via Windows Task Scheduler (requires stable CLI/headless mode first)
@@ -102,81 +445,49 @@ Based on the combined research, the dependency graph from ARCHITECTURE.md and FE
 ### Phase 1: Foundation and Infrastructure
 **Rationale:** All 10 critical pitfalls must be resolved before feature work begins. The dependency graph in FEATURES.md shows that every feature requires the tenant profile registry and session caching layer. Establishing async patterns, error handling, DI container, logging, and JSON persistence now prevents the most expensive retrofits.
 **Delivers:** Runnable WPF shell with tenant selector, multi-tenant session caching (MSAL + MsalCacheHelper), DI container wiring, Serilog logging, SettingsService with write-then-replace persistence, ResX localization scaffolding, shared pagination helper, shared `AsyncRelayCommand` pattern, global exception handlers.
-**Addresses:** Tenant profile registry (prerequisite for all features), EN/FR localization scaffolding, error reporting infrastructure.
-**Avoids:** All 10 pitfalls — async deadlocks, silent errors, token cache races, JSON corruption, ObservableCollection threading, async void, throttling, disposal gaps, trimming.
-**Research flag:** Standard patterns — `Microsoft.Extensions.Hosting` + `CommunityToolkit.Mvvm` + `MsalCacheHelper` are well-documented. No additional research needed.
+**Research flag:** Standard patterns — no additional research needed.

 ### Phase 2: Permissions and Audit Core
-**Rationale:** Permissions reporting is the highest-value daily-use feature and the canonical audit use case. Building it second validates that the auth layer and pagination helper work under real conditions before other features depend on them. It also forces the error reporting UX to be finalized early.
-**Delivers:** Site-level permissions report with recursive scan (configurable depth), CSV export, self-contained HTML export, plain progress feedback ("Scanning X of Y sites"), error surface for failed scans (no silent failures).
-**Addresses:** Permissions report (table stakes P1), CSV + HTML export (table stakes P1), error reporting (table stakes P1).
-**Avoids:** 5,000-item threshold (pagination helper reuse), silent errors (error handling from Phase 1), sync/async deadlock (AsyncRelayCommand from Phase 1).
-**Research flag:** Standard patterns — PnP Framework permission scanning is well-documented. PnP permissions API is HIGH confidence.
+**Rationale:** Permissions reporting is the highest-value daily-use feature and validates the auth layer and pagination helper under real conditions.
+**Delivers:** Site-level permissions report with recursive scan, CSV export, self-contained HTML export, progress feedback, error surface for failed scans.
+**Research flag:** Standard PnP Framework patterns — HIGH confidence.

 ### Phase 3: Storage Metrics and File Operations
-**Rationale:** Storage metrics and file search are the other two daily-use features in the existing tool. They reuse the auth session and export infrastructure from Phases 1–2. Duplicate detection depends on the file enumeration infrastructure built for file search, so these belong together.
-**Delivers:** Storage metrics per site (total + breakdown), file search across sites (KQL-based), duplicate file detection (hash or name+size matching), storage data export (CSV + HTML).
-**Addresses:** Storage metrics (P1), file search (P1), duplicate detection (P1).
-**Avoids:** Large collection streaming (IProgress<T> pattern from Phase 1), Graph SDK pagination (`PageIterator`), API throttling (retry handler from Phase 1).
-**Research flag:** Duplicate detection against large tenants under Graph throttling may need tactical research during planning — hash-based detection at scale has specific pagination constraints.
+**Rationale:** Storage metrics and file search reuse the auth session and export infrastructure from Phases 1–2. Duplicate detection depends on file enumeration built here.
+**Delivers:** Storage metrics, file search (KQL), duplicate detection, storage data export.
+**Research flag:** Duplicate detection at scale under Graph throttling may need targeted research.

 ### Phase 4: Bulk Operations and Provisioning
-**Rationale:** Bulk operations (member add, site creation, transfer) and site/folder template management are the remaining P1 features. They are the highest-complexity features (HIGH implementation cost in FEATURES.md) and benefit from stable async/cancel/progress infrastructure from Phase 1. Folder provisioning depends on site template management — build together.
-**Delivers:** Bulk member add/remove, bulk site creation, ownership transfer, site template capture and apply, folder structure provisioning from template.
-**Addresses:** Bulk operations with progress/cancel (P1), site template management (P1), folder structure provisioning (P1).
-**Avoids:** Operation cancellation (CancellationToken threading from Phase 1), partial-failure reporting (error surface from Phase 2), API throttling (retry handler from Phase 1).
-**Research flag:** PnP Provisioning Engine for site templates may need specific research during planning — template schema and apply behavior are documented but edge cases (Teams-connected sites, modern vs. classic) need validation.
+**Rationale:** Highest-complexity features (bulk writes to client tenants) benefit from stable async/cancel/progress infrastructure from Phase 1.
+**Delivers:** Bulk member add/remove, bulk site creation, ownership transfer, site template capture and apply, folder structure provisioning.
+**Research flag:** PnP Provisioning Engine for Teams-connected sites — edge cases need validation.

 ### Phase 5: New Differentiating Features (v1.x)
-**Rationale:** These three features are new capabilities (not existing-tool parity) that depend on stable v1 infrastructure. User access export across sites requires multi-site permissions scan from Phase 2. Storage charts require storage metrics from Phase 3. Plain-language permissions view is a presentation layer on top of the permissions data model from Phase 2. Grouping them as v1.x avoids blocking the v1 release on new development.
-**Delivers:** User access export across arbitrary site subsets (cross-site access report for a single user), simplified plain-language permissions view (jargon-free labels, color coding), storage graph by file type (pie/bar toggle via ScottPlot.WPF).
-**Addresses:** User access export (P2), simplified permissions view (P2), storage graph by file type (P2).
-**Uses:** ScottPlot.WPF 5.1.57, existing PermissionsService and StorageService from Phases 2–3.
-**Research flag:** User access export across sites involves enumerating group memberships, direct assignments, and inherited access across N sites — the Graph API volume and correct enumeration approach may need targeted research.
+**Rationale:** New capabilities (not existing-tool parity) that depend on stable v1 infrastructure. Group here to avoid blocking the v1 release.
+**Delivers:** User access export across sites, simplified plain-language permissions view, storage graph by file type.
+**Research flag:** User access export — Graph API approach for enumerating all permissions for user X across N sites needs targeted research.

 ### Phase 6: Distribution and Hardening
-**Rationale:** Packaging, end-to-end validation on clean machines, FR locale completeness check, and the "looks done but isn't" checklist from PITFALLS.md. Must be done before any release, not as an afterthought.
-**Delivers:** Single self-contained EXE (`PublishSingleFile=true`, `SelfContained=true`, `PublishTrimmed=false`, `win-x64`), validated on a machine with no .NET runtime, FR locale fully tested, throttling recovery verified, JSON corruption recovery verified, cancellation verified, 5,000+ item library tested.
-**Avoids:** WPF trimming crash (Pitfall 6), "works on dev machine" surprises.
-**Research flag:** Standard patterns — `dotnet publish` single-file configuration is well-documented.
-
-### Phase Ordering Rationale
-
- **Foundation first** is mandatory: all 10 pitfalls map to Phase 1. The auth layer and async patterns are prerequisites for every subsequent phase. Starting features before the foundation is solid replicates the original app's architectural problems.
- **Permissions before storage/search** because permissions validates the pagination helper, auth layer, and export pipeline under real conditions with the most complex data model.
- **Bulk ops and provisioning after core read operations** because they have higher risk (they write to client tenants) and should be tested against a validated auth layer and error surface.
- **New v1.x features after v1 parity** to avoid blocking the release on non-parity features. The three P2 features are all presentation or cross-cutting enhancements on top of stable Phase 2–3 data models.
- **Distribution last** because EXE packaging must be validated against the complete feature set.
-
-### Research Flags
-
-Phases likely needing `/gsd:research-phase` during planning:
- **Phase 3 (Duplicate detection):** Hash-based detection under Graph throttling constraints at large scale — specific pagination strategy and concurrency limits for file enumeration need validation.
- **Phase 4 (Site templates):** PnP Provisioning Engine behavior for Teams-connected sites, modern site template schema edge cases, and apply-template behavior on non-empty sites need verification.
- **Phase 5 (User access export):** Graph API approach for enumerating all permissions for a single user across N sites (group memberships + direct assignments + inherited) — the correct API sequence and volume implications need targeted research.
-
-Phases with standard patterns (skip research-phase):
- **Phase 1 (Foundation):** `Microsoft.Extensions.Hosting` + `CommunityToolkit.Mvvm` + `MsalCacheHelper` patterns are extensively documented in official Microsoft sources.
- **Phase 2 (Permissions):** PnP Framework permission scanning APIs are HIGH confidence from official PnP documentation.
- **Phase 6 (Distribution):** `dotnet publish` single-file configuration is straightforward and well-documented.
+**Rationale:** Packaging, end-to-end validation on clean machines, FR locale completeness, "looks done but isn't" checklist.
+**Delivers:** Single self-contained EXE, validated on a machine with no .NET runtime, all checklist items verified.
+**Research flag:** Standard `dotnet publish` configuration — no additional research needed.

 ## Confidence Assessment

 | Area | Confidence | Notes |
-|------|------------|-------|
-| Stack | HIGH | All package versions verified on NuGet; .NET lifecycle dates confirmed on Microsoft support policy page; PnP.Framework vs PnP.Core SDK choice verified against authoritative GitHub issue |
-| Features | MEDIUM | Microsoft docs (permissions reports, storage reports, Graph API) are HIGH; competitor feature analysis from marketing pages is MEDIUM; no direct API testing performed |
-| Architecture | HIGH | MVVM patterns from Microsoft Learn (official); PnP Framework auth patterns from official PnP docs; `MsalCacheHelper` from official MSAL.NET docs |
-| Pitfalls | HIGH | Critical pitfalls verified via official docs, PnP GitHub issues, and direct audit of the existing codebase (CONCERNS.md); async deadlock and WPF trimming pitfalls confirmed via dotnet/wpf GitHub issues |
+|---|---|---|
+| Stack | HIGH | All package versions verified on NuGet; .NET lifecycle dates confirmed; PnP.Framework vs PnP.Core SDK choice verified |
+| Features | MEDIUM | Microsoft docs HIGH; competitor feature analysis from marketing pages MEDIUM; no direct API testing |
+| Architecture | HIGH | MVVM patterns from Microsoft Learn; PnP Framework auth patterns from official PnP docs; MsalCacheHelper from official MSAL.NET docs |
+| Pitfalls | HIGH | Critical pitfalls verified via official docs, PnP GitHub issues, and direct audit of existing codebase (CONCERNS.md) |

 **Overall confidence:** HIGH

-### Gaps to Address
-
- **PnP Provisioning Engine for Teams-connected sites:** The behavior of `PnP.Framework`'s provisioning engine when applied to Teams-connected modern team sites (vs. classic or communication sites) is not fully documented. Validate during Phase 4 planning with a dedicated research spike.
- **User cross-site access enumeration via Graph API:** The correct Graph API sequence for "all permissions for user X across N sites" (covering group memberships, direct site assignments, and SharePoint group memberships) has multiple possible approaches with different throttling profiles. Validate the most efficient approach during Phase 5 planning.
- **Graph API volume for duplicate detection:** Enumerating file hashes across a large tenant (100k+ files) via `driveItem` Graph calls has unclear throttling limits at that scale. The practical concurrency limit and whether SHA256 computation must happen client-side needs validation.
- **ScottPlot.WPF XAML integration:** ScottPlot 5.x WPF XAML control integration patterns are less documented than the WinForms equivalent. Validate the `WpfPlot` control binding approach during Phase 5 planning.
+**Gaps to address:**
+- PnP Provisioning Engine for Teams-connected sites: behavior not fully documented; validate during Phase 4 planning.
+- User cross-site access enumeration via Graph API: multiple possible approaches with different throttling profiles; validate during Phase 5 planning.
+- Graph API volume for duplicate detection at large scale: practical concurrency limits need validation.
+- ScottPlot.WPF XAML integration: WpfPlot binding patterns less documented than WinForms equivalent; validate during Phase 5 planning.

 ## Sources

@@ -187,26 +498,17 @@ Phases with standard patterns (skip research-phase):
 - Microsoft Learn: SharePoint Online list view threshold — https://learn.microsoft.com/en-us/troubleshoot/sharepoint/lists-and-libraries/items-exceeds-list-view-threshold
 - Microsoft Learn: Graph SDK paging — https://learn.microsoft.com/en-us/graph/sdks/paging
 - Microsoft Learn: Graph throttling guidance — https://learn.microsoft.com/en-us/graph/throttling
- PnP Framework GitHub: https://github.com/pnp/pnpframework — .NET targets, auth patterns
+- PnP Framework GitHub: https://github.com/pnp/pnpframework
 - PnP Framework vs Core authoritative comparison: https://github.com/pnp/pnpframework/issues/620
- PnP Framework auth issues: https://github.com/pnp/pnpframework/issues/961, /447
 - dotnet/wpf trimming issues: https://github.com/dotnet/wpf/issues/4216, /6096
- .NET 10 announcement: https://devblogs.microsoft.com/dotnet/announcing-dotnet-10/
- .NET support policy: https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core
- CommunityToolkit 8.4 announcement: https://devblogs.microsoft.com/dotnet/announcing-the-dotnet-community-toolkit-840/
 - Existing codebase CONCERNS.md audit (2026-04-02)

 ### Secondary (MEDIUM confidence)
 - ShareGate SharePoint audit tool feature page — https://sharegate.com/sharepoint-audit-tool
 - ManageEngine SharePoint Manager Plus — https://www.manageengine.com/sharepoint-management-reporting/sharepoint-permission-auditing-tool.html
 - AdminDroid SharePoint Online auditing — https://admindroid.com/microsoft-365-sharepoint-online-auditing
- sprobot.io: 9 must-have features for SharePoint storage reporting — https://www.sprobot.io/blog/how-to-choose-the-right-sharepoint-storage-reporting-tool-9-must-have-features
- WPF Development Best Practices 2024 — https://medium.com/mesciusinc/wpf-development-best-practices-for-2024-9e5062c71350
- Rick Strahl: Async and Async Void Event Handling in WPF — https://weblog.west-wind.com/posts/2022/Apr/22/Async-and-Async-Void-Event-Handling-in-WPF
-
-### Tertiary (LOW confidence)
- NuGet: ScottPlot.WPF XAML control documentation — sparse; WpfPlot binding patterns need hands-on validation

 ---
-*Research completed: 2026-04-02*
+*v1.0 research completed: 2026-04-02*
+*v2.2 research synthesized: 2026-04-08*
 *Ready for roadmap: yes*
@@ -0,0 +1,130 @@
+using System.IO;
+using System.Text;
+using System.Text.Json;
+using SharepointToolbox.Core.Models;
+using SharepointToolbox.Infrastructure.Persistence;
+
+namespace SharepointToolbox.Tests.Services;
+
+[Trait("Category", "Unit")]
+public class BrandingRepositoryTests : IDisposable
+{
+    private readonly string _tempFile;
+
+    public BrandingRepositoryTests()
+    {
+        _tempFile = Path.GetTempFileName();
+        File.Delete(_tempFile);
+    }
+
+    public void Dispose()
+    {
+        if (File.Exists(_tempFile)) File.Delete(_tempFile);
+        if (File.Exists(_tempFile + ".tmp")) File.Delete(_tempFile + ".tmp");
+    }
+
+    private BrandingRepository CreateRepository() => new(_tempFile);
+
+    [Fact]
+    public async Task LoadAsync_MissingFile_ReturnsDefaultBrandingSettings()
+    {
+        var repo = CreateRepository();
+
+        var settings = await repo.LoadAsync();
+
+        Assert.Null(settings.MspLogo);
+    }
+
+    [Fact]
+    public async Task SaveAndLoad_RoundTrips_MspLogo()
+    {
+        var repo = CreateRepository();
+        var logo = new LogoData { Base64 = "abc123==", MimeType = "image/png" };
+        var original = new BrandingSettings { MspLogo = logo };
+
+        await repo.SaveAsync(original);
+        var loaded = await repo.LoadAsync();
+
+        Assert.NotNull(loaded.MspLogo);
+        Assert.Equal("abc123==", loaded.MspLogo.Base64);
+        Assert.Equal("image/png", loaded.MspLogo.MimeType);
+    }
+
+    [Fact]
+    public async Task SaveAsync_CreatesDirectoryIfNotExists()
+    {
+        var tempDir = Path.Combine(Path.GetTempPath(), Path.GetRandomFileName(), "subdir");
+        var filePath = Path.Combine(tempDir, "branding.json");
+        var repo = new BrandingRepository(filePath);
+
+        try
+        {
+            await repo.SaveAsync(new BrandingSettings());
+            Assert.True(File.Exists(filePath), "File must be created even when directory did not exist");
+        }
+        finally
+        {
+            if (File.Exists(filePath)) File.Delete(filePath);
+            if (Directory.Exists(tempDir)) Directory.Delete(tempDir, recursive: true);
+        }
+    }
+
+    [Fact]
+    public async Task TenantProfile_WithClientLogo_SerializesAndDeserializesCorrectly()
+    {
+        var logo = new LogoData { Base64 = "xyz==", MimeType = "image/jpeg" };
+        var profile = new TenantProfile
+        {
+            Name = "Contoso",
+            TenantUrl = "https://contoso.sharepoint.com",
+            ClientId = "client-id-123",
+            ClientLogo = logo
+        };
+
+        var options = new JsonSerializerOptions
+        {
+            PropertyNamingPolicy = JsonNamingPolicy.CamelCase,
+            WriteIndented = true
+        };
+        var json = JsonSerializer.Serialize(profile, options);
+
+        // Verify camelCase key exists
+        using var doc = JsonDocument.Parse(json);
+        Assert.True(doc.RootElement.TryGetProperty("clientLogo", out var clientLogoElem),
+            "JSON must contain 'clientLogo' key (camelCase)");
+        Assert.Equal(JsonValueKind.Object, clientLogoElem.ValueKind);
+
+        // Deserialize back
+        var readOptions = new JsonSerializerOptions { PropertyNameCaseInsensitive = true };
+        var loaded = JsonSerializer.Deserialize<TenantProfile>(json, readOptions);
+
+        Assert.NotNull(loaded?.ClientLogo);
+        Assert.Equal("xyz==", loaded.ClientLogo.Base64);
+        Assert.Equal("image/jpeg", loaded.ClientLogo.MimeType);
+    }
+
+    [Fact]
+    public async Task TenantProfile_WithoutClientLogo_SerializesWithNullAndDeserializesWithNull()
+    {
+        var profile = new TenantProfile
+        {
+            Name = "Fabrikam",
+            TenantUrl = "https://fabrikam.sharepoint.com",
+            ClientId = "client-id-456"
+        };
+
+        var options = new JsonSerializerOptions
+        {
+            PropertyNamingPolicy = JsonNamingPolicy.CamelCase,
+            WriteIndented = true
+        };
+        var json = JsonSerializer.Serialize(profile, options);
+
+        // Deserialize back — ClientLogo should be null (forward compatible)
+        var readOptions = new JsonSerializerOptions { PropertyNameCaseInsensitive = true };
+        var loaded = JsonSerializer.Deserialize<TenantProfile>(json, readOptions);
+
+        Assert.NotNull(loaded);
+        Assert.Null(loaded.ClientLogo);
+    }
+}
@@ -0,0 +1,223 @@
+using System.Drawing;
+using System.Drawing.Imaging;
+using System.IO;
+using SharepointToolbox.Core.Models;
+using SharepointToolbox.Infrastructure.Persistence;
+using SharepointToolbox.Services;
+
+namespace SharepointToolbox.Tests.Services;
+
+[Trait("Category", "Unit")]
+public class BrandingServiceTests : IDisposable
+{
+    private readonly string _tempRepoFile;
+    private readonly List<string> _tempFiles = new();
+
+    public BrandingServiceTests()
+    {
+        _tempRepoFile = Path.GetTempFileName();
+        File.Delete(_tempRepoFile);
+    }
+
+    public void Dispose()
+    {
+        if (File.Exists(_tempRepoFile)) File.Delete(_tempRepoFile);
+        if (File.Exists(_tempRepoFile + ".tmp")) File.Delete(_tempRepoFile + ".tmp");
+        foreach (var f in _tempFiles)
+        {
+            if (File.Exists(f)) File.Delete(f);
+        }
+    }
+
+    private BrandingRepository CreateRepository() => new(_tempRepoFile);
+    private BrandingService CreateService() => new(CreateRepository());
+
+    private string WriteTempFile(byte[] bytes)
+    {
+        var path = Path.GetTempFileName();
+        File.WriteAllBytes(path, bytes);
+        _tempFiles.Add(path);
+        return path;
+    }
+
+    // Minimal valid 1x1 PNG bytes
+    private static byte[] MinimalPngBytes()
+    {
+        // Full 1x1 transparent PNG (67 bytes)
+        return new byte[]
+        {
+            0x89, 0x50, 0x4E, 0x47, 0x0D, 0x0A, 0x1A, 0x0A, // PNG signature
+            0x00, 0x00, 0x00, 0x0D, // IHDR length
+            0x49, 0x48, 0x44, 0x52, // IHDR
+            0x00, 0x00, 0x00, 0x01, // width = 1
+            0x00, 0x00, 0x00, 0x01, // height = 1
+            0x08, 0x02,             // bit depth = 8, color type = RGB
+            0x00, 0x00, 0x00,       // compression, filter, interlace
+            0x90, 0x77, 0x53, 0xDE, // CRC
+            0x00, 0x00, 0x00, 0x0C, // IDAT length
+            0x49, 0x44, 0x41, 0x54, // IDAT
+            0x08, 0xD7, 0x63, 0xF8, 0xCF, 0xC0, 0x00, 0x00, 0x00, 0x02, 0x00, 0x01, // compressed data
+            0xE2, 0x21, 0xBC, 0x33, // CRC
+            0x00, 0x00, 0x00, 0x00, // IEND length
+            0x49, 0x45, 0x4E, 0x44, // IEND
+            0xAE, 0x42, 0x60, 0x82  // CRC
+        };
+    }
+
+    // Minimal valid JPEG bytes (SOI + APP0 JFIF header + EOI)
+    private static byte[] MinimalJpegBytes()
+    {
+        return new byte[]
+        {
+            0xFF, 0xD8,             // SOI
+            0xFF, 0xE0,             // APP0 marker
+            0x00, 0x10,             // length = 16
+            0x4A, 0x46, 0x49, 0x46, 0x00, // "JFIF\0"
+            0x01, 0x01,             // version 1.1
+            0x00,                   // aspect ratio units = 0
+            0x00, 0x01, 0x00, 0x01, // X/Y density = 1
+            0x00, 0x00,             // thumbnail size
+            0xFF, 0xD9              // EOI
+        };
+    }
+
+    [Fact]
+    public async Task ImportLogoAsync_ValidPng_ReturnsPngLogoData()
+    {
+        var service = CreateService();
+        var pngBytes = MinimalPngBytes();
+        var path = WriteTempFile(pngBytes);
+
+        var result = await service.ImportLogoAsync(path);
+
+        Assert.Equal("image/png", result.MimeType);
+        Assert.Equal(Convert.ToBase64String(pngBytes), result.Base64);
+    }
+
+    [Fact]
+    public async Task ImportLogoAsync_ValidJpeg_ReturnsJpegLogoData()
+    {
+        var service = CreateService();
+        var jpegBytes = MinimalJpegBytes();
+        var path = WriteTempFile(jpegBytes);
+
+        var result = await service.ImportLogoAsync(path);
+
+        Assert.Equal("image/jpeg", result.MimeType);
+    }
+
+    [Fact]
+    public async Task ImportLogoAsync_BmpFile_ThrowsInvalidDataExceptionMentioningPngAndJpg()
+    {
+        var service = CreateService();
+        // BMP magic bytes: 0x42 0x4D
+        var bmpBytes = new byte[] { 0x42, 0x4D, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 };
+        var path = WriteTempFile(bmpBytes);
+
+        var ex = await Assert.ThrowsAsync<InvalidDataException>(() => service.ImportLogoAsync(path));
+        Assert.Contains("PNG", ex.Message, StringComparison.OrdinalIgnoreCase);
+        Assert.Contains("JPG", ex.Message, StringComparison.OrdinalIgnoreCase);
+    }
+
+    [Fact]
+    public async Task ImportLogoAsync_EmptyFile_ThrowsInvalidDataException()
+    {
+        var service = CreateService();
+        var path = WriteTempFile(Array.Empty<byte>());
+
+        await Assert.ThrowsAsync<InvalidDataException>(() => service.ImportLogoAsync(path));
+    }
+
+    [Fact]
+    public async Task ImportLogoAsync_FileUnder512KB_ReturnOriginalBytesUnmodified()
+    {
+        var service = CreateService();
+        var pngBytes = MinimalPngBytes();
+        var path = WriteTempFile(pngBytes);
+
+        var result = await service.ImportLogoAsync(path);
+
+        Assert.Equal(Convert.ToBase64String(pngBytes), result.Base64);
+    }
+
+    [Fact]
+    public async Task ImportLogoAsync_FileOver512KB_ReturnsCompressedUnder512KB()
+    {
+        var service = CreateService();
+
+        // Create a large PNG image in memory (400x400 random pixels)
+        var largePngPath = Path.GetTempFileName();
+        _tempFiles.Add(largePngPath);
+
+        using (var bmp = new Bitmap(400, 400))
+        {
+            var rng = new Random(42);
+            for (int y = 0; y < 400; y++)
+                for (int x = 0; x < 400; x++)
+                    bmp.SetPixel(x, y, Color.FromArgb(255, rng.Next(256), rng.Next(256), rng.Next(256)));
+            bmp.Save(largePngPath, ImageFormat.Png);
+        }
+
+        var fileSize = new FileInfo(largePngPath).Length;
+        // PNG with random pixels should exceed 512 KB
+        // If not, we'll pad it
+        if (fileSize <= 512 * 1024)
+        {
+            // Generate a bigger image to be sure
+            using var bmp = new Bitmap(800, 800);
+            var rng = new Random(42);
+            for (int y = 0; y < 800; y++)
+                for (int x = 0; x < 800; x++)
+                    bmp.SetPixel(x, y, Color.FromArgb(255, rng.Next(256), rng.Next(256), rng.Next(256)));
+            bmp.Save(largePngPath, ImageFormat.Png);
+        }
+
+        fileSize = new FileInfo(largePngPath).Length;
+        Assert.True(fileSize > 512 * 1024, $"Test setup: PNG file must be > 512 KB but was {fileSize} bytes");
+
+        var result = await service.ImportLogoAsync(largePngPath);
+
+        var decodedBytes = Convert.FromBase64String(result.Base64);
+        Assert.True(decodedBytes.Length <= 512 * 1024,
+            $"Compressed result must be <= 512 KB but was {decodedBytes.Length} bytes");
+    }
+
+    [Fact]
+    public async Task SaveMspLogoAsync_PersistsLogoInRepository()
+    {
+        var repo = CreateRepository();
+        var service = new BrandingService(repo);
+        var logo = new LogoData { Base64 = "abc123==", MimeType = "image/png" };
+
+        await service.SaveMspLogoAsync(logo);
+
+        var loaded = await repo.LoadAsync();
+        Assert.NotNull(loaded.MspLogo);
+        Assert.Equal("abc123==", loaded.MspLogo.Base64);
+        Assert.Equal("image/png", loaded.MspLogo.MimeType);
+    }
+
+    [Fact]
+    public async Task ClearMspLogoAsync_SetsMspLogoToNull()
+    {
+        var repo = CreateRepository();
+        var service = new BrandingService(repo);
+        var logo = new LogoData { Base64 = "abc123==", MimeType = "image/png" };
+        await service.SaveMspLogoAsync(logo);
+
+        await service.ClearMspLogoAsync();
+
+        var loaded = await repo.LoadAsync();
+        Assert.Null(loaded.MspLogo);
+    }
+
+    [Fact]
+    public async Task GetMspLogoAsync_WhenNoLogoConfigured_ReturnsNull()
+    {
+        var service = CreateService();
+
+        var result = await service.GetMspLogoAsync();
+
+        Assert.Null(result);
+    }
+}
@@ -0,0 +1,150 @@
+using Microsoft.Graph.Models;
+using SharepointToolbox.Core.Models;
+using SharepointToolbox.Services;
+
+namespace SharepointToolbox.Tests.Services;
+
+/// <summary>
+/// Unit tests for <see cref="GraphUserDirectoryService"/> (Phase 10 Plan 02).
+///
+/// Testing strategy: GraphUserDirectoryService wraps Microsoft Graph SDK's PageIterator,
+/// whose constructor is internal and cannot be mocked without a real GraphServiceClient.
+/// Full pagination/cancellation tests therefore require integration-level setup.
+///
+/// We test what IS unit-testable:
+///   1. MapUser — the static mapping method that converts a Graph User to GraphDirectoryUser.
+///      This covers all 5 required fields and the DisplayName fallback logic.
+///   2. GetUsersAsync integration paths are documented with Skip tests that explain the
+///      constraint and serve as living documentation of intended behaviour.
+/// </summary>
+[Trait("Category", "Unit")]
+public class GraphUserDirectoryServiceTests
+{
+    // ── MapUser: field mapping ────────────────────────────────────────────────
+
+    [Fact]
+    public void MapUser_AllFieldsPresent_MapsCorrectly()
+    {
+        var user = new User
+        {
+            DisplayName = "Alice Smith",
+            UserPrincipalName = "alice@contoso.com",
+            Mail = "alice@contoso.com",
+            Department = "Engineering",
+            JobTitle = "Senior Developer"
+        };
+
+        var result = GraphUserDirectoryService.MapUser(user);
+
+        Assert.Equal("Alice Smith", result.DisplayName);
+        Assert.Equal("alice@contoso.com", result.UserPrincipalName);
+        Assert.Equal("alice@contoso.com", result.Mail);
+        Assert.Equal("Engineering", result.Department);
+        Assert.Equal("Senior Developer", result.JobTitle);
+    }
+
+    [Fact]
+    public void MapUser_NullDisplayName_FallsBackToUserPrincipalName()
+    {
+        var user = new User
+        {
+            DisplayName = null,
+            UserPrincipalName = "bob@contoso.com",
+            Mail = null,
+            Department = null,
+            JobTitle = null
+        };
+
+        var result = GraphUserDirectoryService.MapUser(user);
+
+        Assert.Equal("bob@contoso.com", result.DisplayName);
+        Assert.Equal("bob@contoso.com", result.UserPrincipalName);
+        Assert.Null(result.Mail);
+        Assert.Null(result.Department);
+        Assert.Null(result.JobTitle);
+    }
+
+    [Fact]
+    public void MapUser_NullDisplayNameAndNullUPN_FallsBackToEmptyString()
+    {
+        var user = new User
+        {
+            DisplayName = null,
+            UserPrincipalName = null,
+            Mail = null,
+            Department = null,
+            JobTitle = null
+        };
+
+        var result = GraphUserDirectoryService.MapUser(user);
+
+        Assert.Equal(string.Empty, result.DisplayName);
+        Assert.Equal(string.Empty, result.UserPrincipalName);
+    }
+
+    [Fact]
+    public void MapUser_NullUPN_ReturnsEmptyStringForUPN()
+    {
+        var user = new User
+        {
+            DisplayName = "Carol Jones",
+            UserPrincipalName = null,
+            Mail = "carol@contoso.com",
+            Department = "Marketing",
+            JobTitle = "Manager"
+        };
+
+        var result = GraphUserDirectoryService.MapUser(user);
+
+        Assert.Equal("Carol Jones", result.DisplayName);
+        Assert.Equal(string.Empty, result.UserPrincipalName);
+        Assert.Equal("carol@contoso.com", result.Mail);
+    }
+
+    [Fact]
+    public void MapUser_OptionalFieldsNull_ProducesNullableNullProperties()
+    {
+        var user = new User
+        {
+            DisplayName = "Dave Brown",
+            UserPrincipalName = "dave@contoso.com",
+            Mail = null,
+            Department = null,
+            JobTitle = null
+        };
+
+        var result = GraphUserDirectoryService.MapUser(user);
+
+        Assert.Null(result.Mail);
+        Assert.Null(result.Department);
+        Assert.Null(result.JobTitle);
+    }
+
+    // ── GetUsersAsync: integration-level scenarios (skipped without live tenant) ──
+
+    [Fact(Skip = "Requires integration test with real Graph client — PageIterator.CreatePageIterator " +
+                 "uses internal GraphServiceClient request execution that cannot be mocked via Moq. " +
+                 "Intended behaviour: returns all users matching filter across all pages, " +
+                 "correctly mapping all 5 fields per user.")]
+    public Task GetUsersAsync_SinglePage_ReturnsMappedUsers()
+        => Task.CompletedTask;
+
+    [Fact(Skip = "Requires integration test with real Graph client. " +
+                 "Intended behaviour: IProgress<int>.Report is called once per user " +
+                 "with an incrementing count (1, 2, 3, ...).")]
+    public Task GetUsersAsync_ReportsProgressWithIncrementingCount()
+        => Task.CompletedTask;
+
+    [Fact(Skip = "Requires integration test with real Graph client. " +
+                 "Intended behaviour: when CancellationToken is cancelled during iteration, " +
+                 "the callback returns false and iteration stops, returning partial results " +
+                 "(or OperationCanceledException if cancellation fires before first page).")]
+    public Task GetUsersAsync_CancelledToken_StopsIteration()
+        => Task.CompletedTask;
+
+    [Fact(Skip = "Requires integration test with real Graph client. " +
+                 "Intended behaviour: when Graph returns null response, " +
+                 "GetUsersAsync returns an empty IReadOnlyList without throwing.")]
+    public Task GetUsersAsync_NullResponse_ReturnsEmptyList()
+        => Task.CompletedTask;
+}
@@ -13,7 +13,7 @@ using System.Reflection;
 [assembly: System.Reflection.AssemblyCompanyAttribute("SharepointToolbox.Tests")]
 [assembly: System.Reflection.AssemblyConfigurationAttribute("Debug")]
 [assembly: System.Reflection.AssemblyFileVersionAttribute("1.0.0.0")]
-[assembly: System.Reflection.AssemblyInformationalVersionAttribute("1.0.0+c81d8959f73f4911eec5acd7a0ff4f48d6f69c62")]
+[assembly: System.Reflection.AssemblyInformationalVersionAttribute("1.0.0+9176ae7db931d067f84b7a72ec1460e4d9fa1a45")]
 [assembly: System.Reflection.AssemblyProductAttribute("SharepointToolbox.Tests")]
 [assembly: System.Reflection.AssemblyTitleAttribute("SharepointToolbox.Tests")]
 [assembly: System.Reflection.AssemblyVersionAttribute("1.0.0.0")]
@@ -1 +1 @@
-42315b89ef6a2eb86badcd053748d0a7bdc5a6e3f634442d490c513f6ffcba6a
+3f8ff0168203d2b01c418d674e129581553c2c0acb02df24b6f442c11d07e92d
@@ -1 +1 @@
-7722049415005bc7c5031f47b872fc1ad02fb31cd701bc8587de3e08facab255
+9b3b0f82ba5d0e7afb747bc2e2a3e8c663e5ab3dedc2e90cd2499548ebc0904d
@@ -193,3 +193,21 @@ C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net1
 C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\Std.UriTemplate.dll
 C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\System.ClientModel.dll
 C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\System.Memory.Data.dll
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\HarfBuzzSharp.dll
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\LiveChartsCore.dll
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\LiveChartsCore.SkiaSharpView.dll
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\LiveChartsCore.SkiaSharpView.WPF.dll
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\OpenTK.dll
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\GLWpfControl.dll
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\SkiaSharp.dll
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\SkiaSharp.HarfBuzz.dll
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\SkiaSharp.Views.Desktop.Common.dll
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\SkiaSharp.Views.WPF.dll
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\runtimes\osx\native\libHarfBuzzSharp.dylib
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\runtimes\win-arm64\native\libHarfBuzzSharp.dll
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\runtimes\win-x64\native\libHarfBuzzSharp.dll
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\runtimes\win-x86\native\libHarfBuzzSharp.dll
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\runtimes\osx\native\libSkiaSharp.dylib
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\runtimes\win-arm64\native\libSkiaSharp.dll
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\runtimes\win-x64\native\libSkiaSharp.dll
+C:\Users\dev\Documents\projets\Sharepoint\SharepointToolbox.Tests\bin\Debug\net10.0-windows\runtimes\win-x86\native\libSkiaSharp.dll
@@ -1,6 +1,6 @@
 {
  "version": 2,
-  "dgSpecHash": "qC1LbyrmmpU=",
+  "dgSpecHash": "C7eoEAMdxfU=",
  "success": true,
  "projectFilePath": "C:\\Users\\dev\\Documents\\projets\\Sharepoint\\SharepointToolbox.Tests\\SharepointToolbox.Tests.csproj",
  "expectedPackageFiles": [
@@ -11,6 +11,12 @@
    "C:\\Users\\dev\\.nuget\\packages\\communitytoolkit.mvvm\\8.4.2\\communitytoolkit.mvvm.8.4.2.nupkg.sha512",
    "C:\\Users\\dev\\.nuget\\packages\\coverlet.collector\\6.0.4\\coverlet.collector.6.0.4.nupkg.sha512",
    "C:\\Users\\dev\\.nuget\\packages\\csvhelper\\33.1.0\\csvhelper.33.1.0.nupkg.sha512",
+    "C:\\Users\\dev\\.nuget\\packages\\harfbuzzsharp\\8.3.0.1\\harfbuzzsharp.8.3.0.1.nupkg.sha512",
+    "C:\\Users\\dev\\.nuget\\packages\\harfbuzzsharp.nativeassets.macos\\8.3.0.1\\harfbuzzsharp.nativeassets.macos.8.3.0.1.nupkg.sha512",
+    "C:\\Users\\dev\\.nuget\\packages\\harfbuzzsharp.nativeassets.win32\\8.3.0.1\\harfbuzzsharp.nativeassets.win32.8.3.0.1.nupkg.sha512",
+    "C:\\Users\\dev\\.nuget\\packages\\livechartscore\\2.0.0-rc5.4\\livechartscore.2.0.0-rc5.4.nupkg.sha512",
+    "C:\\Users\\dev\\.nuget\\packages\\livechartscore.skiasharpview\\2.0.0-rc5.4\\livechartscore.skiasharpview.2.0.0-rc5.4.nupkg.sha512",
+    "C:\\Users\\dev\\.nuget\\packages\\livechartscore.skiasharpview.wpf\\2.0.0-rc5.4\\livechartscore.skiasharpview.wpf.2.0.0-rc5.4.nupkg.sha512",
    "C:\\Users\\dev\\.nuget\\packages\\microsoft.applicationinsights\\2.21.0\\microsoft.applicationinsights.2.21.0.nupkg.sha512",
    "C:\\Users\\dev\\.nuget\\packages\\microsoft.bcl.asyncinterfaces\\6.0.0\\microsoft.bcl.asyncinterfaces.6.0.0.nupkg.sha512",
    "C:\\Users\\dev\\.nuget\\packages\\microsoft.codecoverage\\17.14.1\\microsoft.codecoverage.17.14.1.nupkg.sha512",
@@ -70,6 +76,8 @@
    "C:\\Users\\dev\\.nuget\\packages\\microsoft.testplatform.testhost\\17.14.1\\microsoft.testplatform.testhost.17.14.1.nupkg.sha512",
    "C:\\Users\\dev\\.nuget\\packages\\moq\\4.20.72\\moq.4.20.72.nupkg.sha512",
    "C:\\Users\\dev\\.nuget\\packages\\newtonsoft.json\\13.0.3\\newtonsoft.json.13.0.3.nupkg.sha512",
+    "C:\\Users\\dev\\.nuget\\packages\\opentk\\3.3.1\\opentk.3.3.1.nupkg.sha512",
+    "C:\\Users\\dev\\.nuget\\packages\\opentk.glwpfcontrol\\3.3.0\\opentk.glwpfcontrol.3.3.0.nupkg.sha512",
    "C:\\Users\\dev\\.nuget\\packages\\pnp.core\\1.15.0\\pnp.core.1.15.0.nupkg.sha512",
    "C:\\Users\\dev\\.nuget\\packages\\pnp.framework\\1.18.0\\pnp.framework.1.18.0.nupkg.sha512",
    "C:\\Users\\dev\\.nuget\\packages\\portable.xaml\\0.26.0\\portable.xaml.0.26.0.nupkg.sha512",
@@ -77,6 +85,12 @@
    "C:\\Users\\dev\\.nuget\\packages\\serilog.extensions.hosting\\10.0.0\\serilog.extensions.hosting.10.0.0.nupkg.sha512",
    "C:\\Users\\dev\\.nuget\\packages\\serilog.extensions.logging\\10.0.0\\serilog.extensions.logging.10.0.0.nupkg.sha512",
    "C:\\Users\\dev\\.nuget\\packages\\serilog.sinks.file\\7.0.0\\serilog.sinks.file.7.0.0.nupkg.sha512",
+    "C:\\Users\\dev\\.nuget\\packages\\skiasharp\\3.116.1\\skiasharp.3.116.1.nupkg.sha512",
+    "C:\\Users\\dev\\.nuget\\packages\\skiasharp.harfbuzz\\3.116.1\\skiasharp.harfbuzz.3.116.1.nupkg.sha512",
+    "C:\\Users\\dev\\.nuget\\packages\\skiasharp.nativeassets.macos\\3.116.1\\skiasharp.nativeassets.macos.3.116.1.nupkg.sha512",
+    "C:\\Users\\dev\\.nuget\\packages\\skiasharp.nativeassets.win32\\3.116.1\\skiasharp.nativeassets.win32.3.116.1.nupkg.sha512",
+    "C:\\Users\\dev\\.nuget\\packages\\skiasharp.views.desktop.common\\3.116.1\\skiasharp.views.desktop.common.3.116.1.nupkg.sha512",
+    "C:\\Users\\dev\\.nuget\\packages\\skiasharp.views.wpf\\3.116.1\\skiasharp.views.wpf.3.116.1.nupkg.sha512",
    "C:\\Users\\dev\\.nuget\\packages\\std.uritemplate\\2.0.1\\std.uritemplate.2.0.1.nupkg.sha512",
    "C:\\Users\\dev\\.nuget\\packages\\system.clientmodel\\1.1.0\\system.clientmodel.1.1.0.nupkg.sha512",
    "C:\\Users\\dev\\.nuget\\packages\\system.identitymodel.tokens.jwt\\8.6.1\\system.identitymodel.tokens.jwt.8.6.1.nupkg.sha512",
@@ -91,5 +105,42 @@
    "C:\\Users\\dev\\.nuget\\packages\\xunit.extensibility.execution\\2.9.3\\xunit.extensibility.execution.2.9.3.nupkg.sha512",
    "C:\\Users\\dev\\.nuget\\packages\\xunit.runner.visualstudio\\3.1.4\\xunit.runner.visualstudio.3.1.4.nupkg.sha512"
  ],
-  "logs": []
+  "logs": [
+    {
+      "code": "NU1701",
+      "level": "Warning",
+      "message": "Package 'OpenTK 3.3.1' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework 'net10.0-windows7.0'. This package may not be fully compatible with your project.",
+      "projectPath": "C:\\Users\\dev\\Documents\\projets\\Sharepoint\\SharepointToolbox.Tests\\SharepointToolbox.Tests.csproj",
+      "warningLevel": 1,
+      "filePath": "C:\\Users\\dev\\Documents\\projets\\Sharepoint\\SharepointToolbox.Tests\\SharepointToolbox.Tests.csproj",
+      "libraryId": "OpenTK",
+      "targetGraphs": [
+        "net10.0-windows"
+      ]
+    },
+    {
+      "code": "NU1701",
+      "level": "Warning",
+      "message": "Package 'OpenTK.GLWpfControl 3.3.0' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework 'net10.0-windows7.0'. This package may not be fully compatible with your project.",
+      "projectPath": "C:\\Users\\dev\\Documents\\projets\\Sharepoint\\SharepointToolbox.Tests\\SharepointToolbox.Tests.csproj",
+      "warningLevel": 1,
+      "filePath": "C:\\Users\\dev\\Documents\\projets\\Sharepoint\\SharepointToolbox.Tests\\SharepointToolbox.Tests.csproj",
+      "libraryId": "OpenTK.GLWpfControl",
+      "targetGraphs": [
+        "net10.0-windows"
+      ]
+    },
+    {
+      "code": "NU1701",
+      "level": "Warning",
+      "message": "Package 'SkiaSharp.Views.WPF 3.116.1' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework 'net10.0-windows7.0'. This package may not be fully compatible with your project.",
+      "projectPath": "C:\\Users\\dev\\Documents\\projets\\Sharepoint\\SharepointToolbox.Tests\\SharepointToolbox.Tests.csproj",
+      "warningLevel": 1,
+      "filePath": "C:\\Users\\dev\\Documents\\projets\\Sharepoint\\SharepointToolbox.Tests\\SharepointToolbox.Tests.csproj",
+      "libraryId": "SkiaSharp.Views.WPF",
+      "targetGraphs": [
+        "net10.0-windows"
+      ]
+    }
+  ]
 }
@@ -77,6 +77,12 @@ public partial class App : Application
            "SharepointToolbox");
        services.AddSingleton(_ => new ProfileRepository(Path.Combine(appData, "profiles.json")));
        services.AddSingleton(_ => new SettingsRepository(Path.Combine(appData, "settings.json")));
+
+        // Phase 10: Branding Data Foundation
+        services.AddSingleton(_ => new BrandingRepository(Path.Combine(appData, "branding.json")));
+        services.AddSingleton<IBrandingService, BrandingService>();
+        services.AddTransient<IGraphUserDirectoryService, GraphUserDirectoryService>();
+
        services.AddSingleton<MsalClientFactory>();
        services.AddSingleton<SessionManager>();
        services.AddSingleton<ISessionManager>(sp => sp.GetRequiredService<SessionManager>());
@@ -0,0 +1,6 @@
+namespace SharepointToolbox.Core.Models;
+
+public class BrandingSettings
+{
+    public LogoData? MspLogo { get; set; }
+}
@@ -0,0 +1,12 @@
+namespace SharepointToolbox.Core.Models;
+
+/// <summary>
+/// Represents a directory user returned by <see cref="SharepointToolbox.Services.IGraphUserDirectoryService"/>.
+/// Used by Phase 13's User Directory ViewModel to display and filter tenant members.
+/// </summary>
+public record GraphDirectoryUser(
+    string DisplayName,
+    string UserPrincipalName,
+    string? Mail,
+    string? Department,
+    string? JobTitle);
@@ -0,0 +1,7 @@
+namespace SharepointToolbox.Core.Models;
+
+public record LogoData
+{
+    public string Base64 { get; init; } = string.Empty;
+    public string MimeType { get; init; } = string.Empty;
+}
@@ -5,4 +5,5 @@ public class TenantProfile
    public string Name { get; set; } = string.Empty;
    public string TenantUrl { get; set; } = string.Empty;
    public string ClientId { get; set; } = string.Empty;
+    public LogoData? ClientLogo { get; set; }
 }
@@ -0,0 +1,74 @@
+using System.IO;
+using System.Text;
+using System.Text.Json;
+using SharepointToolbox.Core.Models;
+
+namespace SharepointToolbox.Infrastructure.Persistence;
+
+public class BrandingRepository
+{
+    private readonly string _filePath;
+    private readonly SemaphoreSlim _writeLock = new(1, 1);
+
+    public BrandingRepository(string filePath)
+    {
+        _filePath = filePath;
+    }
+
+    public async Task<BrandingSettings> LoadAsync()
+    {
+        if (!File.Exists(_filePath))
+            return new BrandingSettings();
+
+        string json;
+        try
+        {
+            json = await File.ReadAllTextAsync(_filePath, Encoding.UTF8);
+        }
+        catch (IOException ex)
+        {
+            throw new InvalidDataException($"Failed to read branding file: {_filePath}", ex);
+        }
+
+        try
+        {
+            var settings = JsonSerializer.Deserialize<BrandingSettings>(json,
+                new JsonSerializerOptions { PropertyNameCaseInsensitive = true });
+            return settings ?? new BrandingSettings();
+        }
+        catch (JsonException ex)
+        {
+            throw new InvalidDataException($"Branding file contains invalid JSON: {_filePath}", ex);
+        }
+    }
+
+    public async Task SaveAsync(BrandingSettings settings)
+    {
+        await _writeLock.WaitAsync();
+        try
+        {
+            var json = JsonSerializer.Serialize(settings,
+                new JsonSerializerOptions
+                {
+                    WriteIndented = true,
+                    PropertyNamingPolicy = JsonNamingPolicy.CamelCase
+                });
+
+            var tmpPath = _filePath + ".tmp";
+            var dir = Path.GetDirectoryName(_filePath);
+            if (!string.IsNullOrEmpty(dir))
+                Directory.CreateDirectory(dir);
+
+            await File.WriteAllTextAsync(tmpPath, json, Encoding.UTF8);
+
+            // Validate round-trip before replacing
+            JsonDocument.Parse(await File.ReadAllTextAsync(tmpPath, Encoding.UTF8)).Dispose();
+
+            File.Move(tmpPath, _filePath, overwrite: true);
+        }
+        finally
+        {
+            _writeLock.Release();
+        }
+    }
+}
@@ -0,0 +1,152 @@
+using System.IO;
+using System.Windows;
+using System.Windows.Media;
+using System.Windows.Media.Imaging;
+using SharepointToolbox.Core.Models;
+using SharepointToolbox.Infrastructure.Persistence;
+
+namespace SharepointToolbox.Services;
+
+public class BrandingService : IBrandingService
+{
+    private const int MaxSizeBytes = 512 * 1024; // 512 KB
+
+    // PNG signature: first 4 bytes
+    private static readonly byte[] PngMagic = { 0x89, 0x50, 0x4E, 0x47 };
+    // JPEG signature: first 3 bytes
+    private static readonly byte[] JpegMagic = { 0xFF, 0xD8, 0xFF };
+
+    private readonly BrandingRepository _repository;
+
+    public BrandingService(BrandingRepository repository)
+    {
+        _repository = repository;
+    }
+
+    /// <summary>
+    /// Reads a file, validates that it is PNG or JPEG via magic bytes, auto-compresses if over 512 KB,
+    /// and returns a LogoData record. Does NOT persist anything — the caller decides where to store it.
+    /// </summary>
+    public async Task<LogoData> ImportLogoAsync(string filePath)
+    {
+        var bytes = await File.ReadAllBytesAsync(filePath);
+
+        var mimeType = DetectMimeType(bytes);
+
+        if (bytes.Length > MaxSizeBytes)
+        {
+            bytes = CompressToLimit(bytes, mimeType, MaxSizeBytes);
+        }
+
+        return new LogoData
+        {
+            Base64 = Convert.ToBase64String(bytes),
+            MimeType = mimeType
+        };
+    }
+
+    public async Task SaveMspLogoAsync(LogoData logo)
+    {
+        var settings = await _repository.LoadAsync();
+        settings.MspLogo = logo;
+        await _repository.SaveAsync(settings);
+    }
+
+    public async Task ClearMspLogoAsync()
+    {
+        var settings = await _repository.LoadAsync();
+        settings.MspLogo = null;
+        await _repository.SaveAsync(settings);
+    }
+
+    public async Task<LogoData?> GetMspLogoAsync()
+    {
+        var settings = await _repository.LoadAsync();
+        return settings.MspLogo;
+    }
+
+    // -------------------------------------------------------------------------
+    // Private helpers
+    // -------------------------------------------------------------------------
+
+    private static string DetectMimeType(byte[] bytes)
+    {
+        if (bytes.Length == 0)
+            throw new InvalidDataException("File is empty. Only PNG and JPG files are accepted.");
+
+        if (bytes.Length >= 4 && bytes[0] == PngMagic[0] && bytes[1] == PngMagic[1]
+                               && bytes[2] == PngMagic[2] && bytes[3] == PngMagic[3])
+            return "image/png";
+
+        if (bytes.Length >= 3 && bytes[0] == JpegMagic[0] && bytes[1] == JpegMagic[1]
+                               && bytes[2] == JpegMagic[2])
+            return "image/jpeg";
+
+        throw new InvalidDataException(
+            "File format is not PNG or JPG. Only PNG and JPG are accepted.");
+    }
+
+    /// <summary>
+    /// Compresses image bytes using WPF imaging (PresentationCore) to fit within <paramref name="maxBytes"/>.
+    /// Resizes proportionally to max 300x300 at quality 75 first pass; if still too large, 200x200 at quality 50.
+    /// </summary>
+    private static byte[] CompressToLimit(byte[] bytes, string mimeType, int maxBytes)
+    {
+        // First pass: resize to 300x300 max, quality 75
+        var compressed = ResizeAndEncode(bytes, mimeType, 300, 75);
+        if (compressed.Length <= maxBytes)
+            return compressed;
+
+        // Second pass: resize to 200x200 max, quality 50
+        compressed = ResizeAndEncode(bytes, mimeType, 200, 50);
+        return compressed;
+    }
+
+    private static byte[] ResizeAndEncode(byte[] originalBytes, string mimeType, int maxDimension, int quality)
+    {
+        // Decode source image using WPF BitmapDecoder
+        using var inputStream = new MemoryStream(originalBytes);
+        var decoder = BitmapDecoder.Create(
+            inputStream,
+            BitmapCreateOptions.PreservePixelFormat,
+            BitmapCacheOption.OnLoad);
+
+        var frame = decoder.Frames[0];
+
+        // Calculate target dimensions (proportional scaling)
+        double srcWidth = frame.PixelWidth;
+        double srcHeight = frame.PixelHeight;
+        double scale = Math.Min((double)maxDimension / srcWidth, (double)maxDimension / srcHeight);
+
+        // Only scale down, never up
+        if (scale >= 1.0)
+            scale = 1.0;
+
+        int targetWidth = Math.Max(1, (int)(srcWidth * scale));
+        int targetHeight = Math.Max(1, (int)(srcHeight * scale));
+
+        // Scale the bitmap using TransformedBitmap
+        var scaledBitmap = new TransformedBitmap(
+            frame,
+            new ScaleTransform(scale, scale));
+
+        // Encode to target format
+        using var outputStream = new MemoryStream();
+        BitmapEncoder encoder = mimeType == "image/png"
+            ? new PngBitmapEncoder()
+            : CreateJpegEncoder(quality);
+
+        encoder.Frames.Add(BitmapFrame.Create(scaledBitmap));
+        encoder.Save(outputStream);
+
+        return outputStream.ToArray();
+    }
+
+    private static BitmapEncoder CreateJpegEncoder(int quality)
+    {
+        return new JpegBitmapEncoder
+        {
+            QualityLevel = quality
+        };
+    }
+}
@@ -0,0 +1,78 @@
+using Microsoft.Graph;
+using Microsoft.Graph.Models;
+using SharepointToolbox.Core.Models;
+using AppGraphClientFactory = SharepointToolbox.Infrastructure.Auth.GraphClientFactory;
+
+namespace SharepointToolbox.Services;
+
+/// <summary>
+/// Enumerates all enabled member users from a tenant via Microsoft Graph,
+/// using PageIterator for transparent multi-page iteration.
+/// Used by Phase 13's User Directory ViewModel.
+/// </summary>
+public class GraphUserDirectoryService : IGraphUserDirectoryService
+{
+    private readonly AppGraphClientFactory _graphClientFactory;
+
+    public GraphUserDirectoryService(AppGraphClientFactory graphClientFactory)
+    {
+        _graphClientFactory = graphClientFactory;
+    }
+
+    /// <inheritdoc />
+    public async Task<IReadOnlyList<GraphDirectoryUser>> GetUsersAsync(
+        string clientId,
+        IProgress<int>? progress = null,
+        CancellationToken ct = default)
+    {
+        var graphClient = await _graphClientFactory.CreateClientAsync(clientId, ct);
+
+        var response = await graphClient.Users.GetAsync(config =>
+        {
+            // Pending real-tenant verification — see STATE.md pending todos
+            config.QueryParameters.Filter = "accountEnabled eq true and userType eq 'Member'";
+            config.QueryParameters.Select = new[]
+            {
+                "displayName", "userPrincipalName", "mail", "department", "jobTitle"
+            };
+            config.QueryParameters.Top = 999;
+            // No ConsistencyLevel header: standard equality filter does not require eventual consistency
+        }, ct);
+
+        if (response is null)
+            return Array.Empty<GraphDirectoryUser>();
+
+        var results = new List<GraphDirectoryUser>();
+
+        var pageIterator = PageIterator<User, UserCollectionResponse>.CreatePageIterator(
+            graphClient,
+            response,
+            user =>
+            {
+                // Honour cancellation inside the callback — returning false stops iteration
+                if (ct.IsCancellationRequested)
+                    return false;
+
+                results.Add(MapUser(user));
+                progress?.Report(results.Count);
+                return true;
+            });
+
+        await pageIterator.IterateAsync(ct);
+
+        return results;
+    }
+
+    /// <summary>
+    /// Maps a Graph SDK <see cref="User"/> object to a <see cref="GraphDirectoryUser"/> record.
+    /// Extracted as an internal static method to allow direct unit-test coverage of mapping logic
+    /// without requiring a live Graph endpoint.
+    /// </summary>
+    internal static GraphDirectoryUser MapUser(User user) =>
+        new(
+            DisplayName: user.DisplayName ?? user.UserPrincipalName ?? string.Empty,
+            UserPrincipalName: user.UserPrincipalName ?? string.Empty,
+            Mail: user.Mail,
+            Department: user.Department,
+            JobTitle: user.JobTitle);
+}
@@ -0,0 +1,11 @@
+using SharepointToolbox.Core.Models;
+
+namespace SharepointToolbox.Services;
+
+public interface IBrandingService
+{
+    Task<LogoData> ImportLogoAsync(string filePath);
+    Task SaveMspLogoAsync(LogoData logo);
+    Task ClearMspLogoAsync();
+    Task<LogoData?> GetMspLogoAsync();
+}
@@ -0,0 +1,26 @@
+using SharepointToolbox.Core.Models;
+
+namespace SharepointToolbox.Services;
+
+/// <summary>
+/// Enumerates all enabled member users from a tenant via Microsoft Graph.
+/// Used by Phase 13's User Directory ViewModel to populate the browse grid.
+/// </summary>
+public interface IGraphUserDirectoryService
+{
+    /// <summary>
+    /// Returns all enabled member users in the tenant associated with <paramref name="clientId"/>.
+    /// Iterates through all pages using the Graph SDK PageIterator until exhausted or cancelled.
+    /// </summary>
+    /// <param name="clientId">The client/tenant identifier used to obtain a Graph token.</param>
+    /// <param name="progress">
+    /// Optional progress reporter — receives the running count of users fetched so far.
+    /// Phase 13's ViewModel uses this to show "Loading... X users" feedback.
+    /// Pass <c>null</c> for no progress reporting.
+    /// </param>
+    /// <param name="ct">Cancellation token. Iteration stops when cancelled.</param>
+    Task<IReadOnlyList<GraphDirectoryUser>> GetUsersAsync(
+        string clientId,
+        IProgress<int>? progress = null,
+        CancellationToken ct = default);
+}
@@ -1,4 +1,4 @@
-#pragma checksum "..\..\..\MainWindow.xaml" "{ff1816ec-aa5e-4d10-87f7-6f4963833460}" "05347FA2DBD20FB75D5346B7F8B40DAECC90BF94"
+#pragma checksum "..\..\..\MainWindow.xaml" "{ff1816ec-aa5e-4d10-87f7-6f4963833460}" "D245D7A48B1C376DBC3E928C8803B8F6A796CAB7"
 //------------------------------------------------------------------------------
 // <auto-generated>
 //     This code was generated by a tool.
@@ -42,7 +42,7 @@ namespace SharepointToolbox {
    public partial class MainWindow : System.Windows.Window, System.Windows.Markup.IComponentConnector {
        
        
-        #line 37 "..\..\..\MainWindow.xaml"
+        #line 44 "..\..\..\MainWindow.xaml"
        [System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.Performance", "CA1823:AvoidUnusedPrivateFields")]
        internal System.Windows.Controls.RichTextBox LogPanel;
        
@@ -50,7 +50,7 @@ namespace SharepointToolbox {
        #line hidden
        
        
-        #line 44 "..\..\..\MainWindow.xaml"
+        #line 51 "..\..\..\MainWindow.xaml"
        [System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.Performance", "CA1823:AvoidUnusedPrivateFields")]
        internal System.Windows.Controls.TabItem PermissionsTabItem;
        
@@ -58,7 +58,7 @@ namespace SharepointToolbox {
        #line hidden
        
        
-        #line 47 "..\..\..\MainWindow.xaml"
+        #line 54 "..\..\..\MainWindow.xaml"
        [System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.Performance", "CA1823:AvoidUnusedPrivateFields")]
        internal System.Windows.Controls.TabItem StorageTabItem;
        
@@ -66,7 +66,7 @@ namespace SharepointToolbox {
        #line hidden
        
        
-        #line 50 "..\..\..\MainWindow.xaml"
+        #line 57 "..\..\..\MainWindow.xaml"
        [System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.Performance", "CA1823:AvoidUnusedPrivateFields")]
        internal System.Windows.Controls.TabItem SearchTabItem;
        
@@ -74,7 +74,7 @@ namespace SharepointToolbox {
        #line hidden
        
        
-        #line 53 "..\..\..\MainWindow.xaml"
+        #line 60 "..\..\..\MainWindow.xaml"
        [System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.Performance", "CA1823:AvoidUnusedPrivateFields")]
        internal System.Windows.Controls.TabItem DuplicatesTabItem;
        
@@ -82,7 +82,7 @@ namespace SharepointToolbox {
        #line hidden
        
        
-        #line 56 "..\..\..\MainWindow.xaml"
+        #line 63 "..\..\..\MainWindow.xaml"
        [System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.Performance", "CA1823:AvoidUnusedPrivateFields")]
        internal System.Windows.Controls.TabItem TransferTabItem;
        
@@ -90,7 +90,7 @@ namespace SharepointToolbox {
        #line hidden
        
        
-        #line 59 "..\..\..\MainWindow.xaml"
+        #line 66 "..\..\..\MainWindow.xaml"
        [System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.Performance", "CA1823:AvoidUnusedPrivateFields")]
        internal System.Windows.Controls.TabItem BulkMembersTabItem;
        
@@ -98,7 +98,7 @@ namespace SharepointToolbox {
        #line hidden
        
        
-        #line 62 "..\..\..\MainWindow.xaml"
+        #line 69 "..\..\..\MainWindow.xaml"
        [System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.Performance", "CA1823:AvoidUnusedPrivateFields")]
        internal System.Windows.Controls.TabItem BulkSitesTabItem;
        
@@ -106,7 +106,7 @@ namespace SharepointToolbox {
        #line hidden
        
        
-        #line 65 "..\..\..\MainWindow.xaml"
+        #line 72 "..\..\..\MainWindow.xaml"
        [System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.Performance", "CA1823:AvoidUnusedPrivateFields")]
        internal System.Windows.Controls.TabItem FolderStructureTabItem;
        
@@ -114,7 +114,7 @@ namespace SharepointToolbox {
        #line hidden
        
        
-        #line 68 "..\..\..\MainWindow.xaml"
+        #line 75 "..\..\..\MainWindow.xaml"
        [System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.Performance", "CA1823:AvoidUnusedPrivateFields")]
        internal System.Windows.Controls.TabItem TemplatesTabItem;
        
@@ -122,7 +122,15 @@ namespace SharepointToolbox {
        #line hidden
        
        
-        #line 72 "..\..\..\MainWindow.xaml"
+        #line 79 "..\..\..\MainWindow.xaml"
+        [System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.Performance", "CA1823:AvoidUnusedPrivateFields")]
+        internal System.Windows.Controls.TabItem UserAccessAuditTabItem;
+        
+        #line default
+        #line hidden
+        
+        
+        #line 83 "..\..\..\MainWindow.xaml"
        [System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("Microsoft.Performance", "CA1823:AvoidUnusedPrivateFields")]
        internal System.Windows.Controls.TabItem SettingsTabItem;
        
@@ -190,6 +198,9 @@ namespace SharepointToolbox {
            this.TemplatesTabItem = ((System.Windows.Controls.TabItem)(target));
            return;
            case 11:
+            this.UserAccessAuditTabItem = ((System.Windows.Controls.TabItem)(target));
+            return;
+            case 12:
            this.SettingsTabItem = ((System.Windows.Controls.TabItem)(target));
            return;
            }
@@ -13,7 +13,7 @@ using System.Reflection;
 [assembly: System.Reflection.AssemblyCompanyAttribute("SharepointToolbox")]
 [assembly: System.Reflection.AssemblyConfigurationAttribute("Debug")]
 [assembly: System.Reflection.AssemblyFileVersionAttribute("1.0.0.0")]
-[assembly: System.Reflection.AssemblyInformationalVersionAttribute("1.0.0+c81d8959f73f4911eec5acd7a0ff4f48d6f69c62")]
+[assembly: System.Reflection.AssemblyInformationalVersionAttribute("1.0.0+9176ae7db931d067f84b7a72ec1460e4d9fa1a45")]
 [assembly: System.Reflection.AssemblyProductAttribute("SharepointToolbox")]
 [assembly: System.Reflection.AssemblyTitleAttribute("SharepointToolbox")]
 [assembly: System.Reflection.AssemblyVersionAttribute("1.0.0.0")]
@@ -1 +1 @@
-b94c8bd3a2bfbf219c1ffa7f8e05f418a2d4e3466fe4ca36ec6595364f035763
+a9f27f31a08398aac4f03e3e63fabad61340e40ec0164f0e80bdbe015af66c82
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Dev	e9a1530120	docs(phase-10): complete phase execution and verification Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-08 13:30:23 +02:00
Dev	9176ae7db9	docs(10-03): complete branding-data-foundation plan 03 - 10-03-SUMMARY.md: DI registration for Phase 10 services - STATE.md: advanced position, added decision, updated session - ROADMAP.md: phase 10 marked complete (3/3 plans)	2026-04-08 12:37:15 +02:00
Dev	7e8e228155	feat(10-03): register Phase 10 services in DI container - Add BrandingRepository as Singleton with branding.json path - Add IBrandingService/BrandingService as Singleton - Add IGraphUserDirectoryService/GraphUserDirectoryService as Transient - 224 tests pass, 26 integration tests skipped (live Graph)	2026-04-08 12:36:12 +02:00
Dev	61d7ada945	docs(10-01): complete branding-data-foundation plan 01 - Add 10-01-SUMMARY.md with task commits, deviation doc, and dependency graph - Update STATE.md: decisions logged, session updated - Update ROADMAP.md: phase 10 In Progress (1/3 plans complete) - Mark BRAND-01, BRAND-03 complete in REQUIREMENTS.md	2026-04-08 12:33:57 +02:00
Dev	188a8a7fff	docs(10-02): complete Graph user directory service plan - SUMMARY: GraphDirectoryUser model, IGraphUserDirectoryService, GraphUserDirectoryService with PageIterator - STATE: decisions added, session updated, progress bar updated - ROADMAP: phase 10 marked In Progress (2/3 summaries) - REQUIREMENTS: BRAND-06 marked complete - Deferred: BrandingServiceTests.cs blocking test compilation (pre-existing, plan 10-01 artifact)	2026-04-08 12:33:33 +02:00
Dev	130386622f	feat(10-01): create BrandingService with magic byte validation and auto-compression - Add IBrandingService interface with ImportLogoAsync, Save/Clear/GetMspLogoAsync - Add BrandingService: PNG/JPEG magic byte detection, rejects unsupported formats with descriptive error, auto-compresses files over 512 KB using WPF PresentationCore imaging - Add BrandingServiceTests: 9 tests covering validation, rejection, compression, CRUD - Deviation: used WPF BitmapEncoder/TransformedBitmap instead of System.Drawing.Bitmap (System.Drawing.Common not available without new NuGet package; WPF PresentationCore is in the existing stack per architectural decisions)	2026-04-08 12:32:23 +02:00
Dev	3ba574612f	feat(10-02): implement GraphUserDirectoryService with PageIterator and unit tests - GraphUserDirectoryService uses PageIterator<User, UserCollectionResponse> for pagination - Filter: accountEnabled eq true and userType eq 'Member' (no ConsistencyLevel header) - Cancellation checked in PageIterator callback (return false stops iteration) - Progress reported via IProgress<int> with running count per user - MapUser extracted as internal static for direct unit test coverage - Tests: 5 unit tests for MapUser field mapping and fallback logic - Integration-level tests (pagination/cancellation) skipped with rationale documented - Note: test project compilation blocked by pre-existing BrandingServiceTests.cs (10-01 artifact)	2026-04-08 12:32:04 +02:00
Dev	2280f12eab	feat(10-01): create logo models, BrandingRepository, and repository tests - Add LogoData record with Base64 and MimeType init properties - Add BrandingSettings class with nullable MspLogo property - Extend TenantProfile with nullable ClientLogo property (additive) - Add BrandingRepository mirroring SettingsRepository pattern (write-then-replace) - Add BrandingRepositoryTests: 5 tests covering load defaults, round-trip, dir creation, and TenantProfile serialization	2026-04-08 12:29:53 +02:00
Dev	5e56a96cd0	feat(10-02): add GraphDirectoryUser model and IGraphUserDirectoryService interface - GraphDirectoryUser positional record with DisplayName, UPN, Mail, Department, JobTitle - IGraphUserDirectoryService.GetUsersAsync with clientId, IProgress<int>?, CancellationToken - Follows existing GraphUserSearchService namespace pattern	2026-04-08 12:29:19 +02:00
Dev	1ffd71243e	docs(10): create phase plan - 3 plans in 2 waves Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-08 11:50:59 +02:00
Dev	464b70ddcc	docs(phase-10): add context, research, and validation strategy Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-08 11:44:24 +02:00
Dev	e6fdccf19c	docs(phase-10): research branding data foundation Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-04-08 11:43:07 +02:00
Dev	59ff5184ff	docs: create milestone v2.2 roadmap (5 phases, 11 requirements) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-08 11:22:05 +02:00
Dev	5ccf1688ea	docs: define milestone v2.2 requirements (11 requirements) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-08 11:00:59 +02:00
Dev	5f59e339ee	docs(research): synthesize v2.2 research into SUMMARY.md Adds v2.2 milestone section (Report Branding & User Directory) while preserving the original v1.0 summary. Covers stack additions (none), feature table stakes vs. differentiators, architecture integration points with dependency-aware build order, top 6 critical pitfalls with prevention strategies, suggested roadmap phase structure, open product questions, and confidence assessment. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-04-08 10:58:57 +02:00
Dev	8447e78db9	docs: start milestone v2.2 Report Branding & User Directory Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-08 10:57:27 +02:00