∞Modern Support Consult∞
Anchored assessment
⑦①②⓪③

MSC is a Windows app built for IT professionals on desktop and laptop devices; it is not intended for mobile use (except lightweight scenarios).

Modern Support Consult provides precision assessment for IT Messaging scenarios (Microsoft Exchange On-prem, Hybrid & Online).
Now that official support for legacy versions of Exchange Server has ended, MSC is here to fill the potential gap in the public market.
We have consolidated a professional lifetime of experience and know-how at the certified master level into our core intel.

Mode
Theme
Modern consult
Speed • Clarity • Proof
What took hours, now takes a few minutes > Work of weeks, done in days
Fast baselines, clear decisions, measurable proof — tuned to your environment.
30 MINS of your time→Reach Amplify stage→Deliver Plan de Campagne
Signal feed
live
What took hours → now takes minutes
Open portal — Start here
LuiT is Microsoft AI-Cloud
Partner and is participating
in its ISV Success
Program
to see if we understand why you arrived on our MSC Portal?
⟐⌁◈⌂✦★✎⛨
Page 2 · Why you arrived

When a “support case” becomes a program

Your situation spans environment, policy, risk, timelines, and ownership — you need an adjustable program, not a ticket.
You’re here because your situation goes beyond a single product ticket. The real problem spans environment, policy, risk, timelines, and ownership — and you need a path that keeps your IT team in control.
Fit-first exploration, not license-first commitment
Exact-fit guidance (not generic tooling)
The “last 20%” is where projects stall: hybrid reality, exceptions, approvals, and change windows. You need guidance that fits your environment.
Empower IT (keep accountability)
Clear owners, explicit decisions, and runnable artifacts your team can execute — with humans accountable and automation predictable.
A plan that learns
A roadmap that updates as signals and constraints change — with traceable rationale, not magic.
Secure exploration before commitment
Explore roadmap options safely before committing to expensive licenses or an inflexible suite.
Why customers arrive
control • fit • learning loop
Hybrid environmentM365 • Entra • on-prem • appsNon-standard scenarioconstraints • exceptions • edge casesRisk & ownershipgovernance • audit • change windowsAdjustable roadmapnot a one-size suiteIT stays in controlAI assistw/ guardrails
When the case is bigger than “support”, you need a loop that can be tuned mid-flight — with humans accountable and automation predictable.
⟐⌁◈⌂✦★✎⛨
Page 3 · Demo journey

Open a scenario. Follow the artifacts. Keep control.

Pick a scenario, then inspect baseline → decisions → roadmap → proof.
This portal shows what a Modern Support Consult looks like in practice: scenario-based journeys with real, exportable artifacts. Pick one of the messaging scenarios below and walk the same loop we use with customers.
Browse all demos →How evidence works →
The demo journey (what to look for)
  1. 1. Start at baseline: scope, assumptions, and signals.
  2. 2. Read the decision notes: risk, impact, owner, next action.
  3. 3. Follow the roadmap/runbook: prerequisites, rollout, rollback, validation.
  4. 4. Check proof: before/after deltas and sign-off readiness.
AI in the demos
AI accelerates analysis (structure, summaries, trade-offs). Humans approve change — your IT stays in control.
Mail securityLock protection
Demo scenario · Validate
Email Security Snapshot (DNS signals)
A compact signal snapshot: checks, outcomes, and recommended actions (customer-ready HTML).
Controls snapshotAction listCustomer-ready HTML
Open artifacts →
Microsoft DefenderExchange access
Demo scenario · Architect
E-mail Security Fix-up Plan
Architect-stage roadmap bundle: overview, actions, summary, risk register, and a runbook.
Prioritized phasesRisk register
Open artifacts →
Demo scenario · Consider
Optimize Outlook
Consider-stage projection with timeline, capacity planning, milestones, and risk assessment.
Timeline + milestonesCapacity planningRisk register
Open artifacts →
⟐⌁◈⌂✦★✎⛨
Page 4 · Business model

Explore free. Pay at Amplify to unlock unlimited recurring usage.

Assisted starts with a €250 kickoff. Buy the full scenario at Amplify for unlimited recurring usage and configurable report detail.
Free: Consider + Architect + Validate to confirm fit and shape a safe plan.

Amplify: checkout for the full scenario. After unlock: unlimited recurring usage, and report bundle detail level becomes configurable.

Assisted: €250 entrance fee before Consider, then the same stages with you.

Promo: Email Security Snapshot → E-mail Security Fix-up Plan starts activation at the Snapshot.
Commercial clarity without oversharing paid deliverables
Activation map
A compact view of what’s free vs what triggers activation.
FreeActivationPromo exception
MSC activation diagramMost scenarios: Consider, Architect, and Validate are free. Checkout happens at Amplify (full scenario) and unlocks unlimited recurring usage with configurable report detail. Assisted engagements start with a €250 entrance fee before Consider. Email Security Snapshot promo activates at Snapshot.Assisted: €250 entrance fee → kickoffConsiderArchitectValidateAmplifycheckout / proof gateOnline runsCheckout → full assessmentUnlimited recurring usagePromo: Email Security Snapshot → E-mail Security Fix-up Planactivation starts at Snapshot (opening action)
Free stages
Use Consider + Architect + Validate to confirm fit and plan safely.
Checkout / proof gate
Checkout at Amplify unlocks unlimited recurring usage. Report detail becomes configurable.
Assisted activation
Assisted starts with a €250 entrance fee kickoff before Consider.
Promo exception
Email Security Snapshot → E-mail Security Fix-up Plan starts activation at Snapshot.
⟐⌁◈⌂✦★✎⛨
Page 5 · Deployment model value

Secure by design: static UI, public API, customer-owned outputs

Client-side first. No secrets in the browser. No customer content parked in MSC storage.
MSC is built to be safe for static hosting and strict boundaries: the UI is a static export, browser calls target a single public API base URL, and your artifact bundles land in customer-owned storage.
Read more →SWA-safe by default • Least-privilege posture
One-line promise
Customer data does not persist in MSC backend storage.
Outputs go to customer-owned destinations (your workspace, your retention, your controls).
Trust boundary (at a glance)
The portal is static, calls only the public API, and writes outputs to a destination you control.
SWA-safe
Browser
Static portal UI
→
Public API
No secrets in UI
→
Customer storage
Your workspace / bucket
MSC backend storage
Not used for customer content. Artifacts are routed to customer-owned destinations.
✕
Runs client-side
Static app. Most interaction happens in your browser—no privileged UI sessions.
  • ✓Safe for static hosting (Azure Static Web Apps export)
  • ✓Browser calls only target the public API base URL
  • ✓No tenant credentials embedded in the UI
Audit + governance friendly
Deterministic artifact bundles with journey IDs—easy to review, easy to sign off.
  • •Least-privilege design (no “super admin” dependency)
  • •Clear provenance: journey IDs + repeatable outputs
  • •Bring-your-own workspace for retention and approvals
Customer-owned destinations
Artifact bundles can be routed into storage/workspaces owned and controlled by the customer.
  • •Azure Blob / Storage account containers
  • •AWS S3 / GCS buckets (customer-managed)
  • •SharePoint / OneDrive / file shares (customer workspace)
What we do / don’t store
We keep (for the run)
  • •Journey IDs + status
  • •Deterministic summaries/metadata
  • •Export links (to your destination)
We never park
  • •Tenant admin credentials
  • •Customer datasets/content
  • •Long-term artifact storage
⟐⌁◈⌂✦★✎⛨
Page 6 · The Portal Surfaces

Three panels, one narrative

Winsight delivers evidence-first intel. Journeye keeps the spine coherent. Operandum steers emphasis without touching authorization.

Abstract. Winsight Engine

Winsight

Metaflow Insight · Evidence-first intel

Decisions
12
Candidates
7
Guidances
4
Waivers
2
Intel Trail23
Signals156
Activity8
LikelihoodHigh
Strategic · Tactical · Analytical · Likelihood intel

Journeye

Revelation · Journey spine & narrative

Identity & Access
Discovery
Data Classification
Analysis
Network Segmentation
Planning
Portflow Artifacts
Architecture DiagramRisk MatrixMigration TimelineApproval Gate
↗Share URL available · journey stays coherent
Keeps stage, runs, and decisions reviewable

Operandum

Organization profile · Customer-safe steering

Delivery Style
AgileDevOps
Shapes phrasing & emphasis, not authorization
⟐⌁◈⌂✦★✎⛨
Page 7 · Success stories

What “added value” looks like when it hits production

Representative outcomes (no customer names) focused on artifacts that survive governance.
Short examples of what customers get: clear decisions, proof, and artifacts teams can execute.
Outcomes first. Evidence always.
NDES recovery for a government environment
Certificate enrollment outage · devices failing to obtain certs · operational and compliance pressure
Challenge
NDES certificate enrollment failed in production under strict change control and limited access windows.
What MSC did
  • •Collected key evidence (errors, connectivity signals, template indicators).
  • •Produced a prioritized fix-up plan with explicit owners.
  • •Validated recovery with a short before/after checklist.
Outcome
  • •Enrollment restored with a proof trail (before/after checkpoints).
  • •Faster execution via a deterministic action list.
  • •Auditable sign-off readiness.
Customer identity is intentionally omitted. These are representative engagement patterns, not public case studies.
Exchange Online onboarding for a university
Tenant onboarding · identity & mail flow readiness · phased rollout under academic calendar pressure
Challenge
A university needed a safe, phased Exchange Online onboarding plan with tight change windows, mixed client populations, and a strong governance/audit posture.
What MSC did
  • •Mapped prerequisites and constraints (identity, domains, mail flow, client readiness, stakeholder approvals).
  • •Built an executable rollout plan with decision points, backout steps, and validation checkpoints.
  • •Produced stakeholder-ready artifacts (risk register, comms plan, and runbook-style checklists).
Outcome
  • •A governance-friendly onboarding blueprint that survived review and could be executed by the ops team.
  • •Reduced rollout risk through explicit checkpoints, ownership, and backout readiness.
  • •Faster alignment across IT + security + faculty stakeholders via clear artifacts and decision logs.
Customer identity is intentionally omitted. These are representative engagement patterns, not public case studies.
⟐⌁◈⌂✦★✎⛨
Page 8 · Request a scenario

Your scenario isn’t on the list? Request it.

Tell us the outcome and constraints — we’ll craft a repeatable scenario with evidence and artifacts.
MSC’s strongest specialization is messaging and collaboration — but we can craft custom scenarios for virtually any Microsoft 365, Azure, or hybrid construct, aligned to the outcome you want. New scenarios can be requested and shaped quickly.
What you can request
A scenario is a repeatable blueprint: signals → decisions → artifacts → proof.
  • •Identity posture, conditional access, access reviews
  • •Messaging security and hygiene improvements
  • •Hybrid onboarding, readiness, migration wave design
  • •Compliance, retention, eDiscovery readiness
  • •Operational readiness and runbook creation
How fast it happens
Short shaping loop to lock scope and outputs, then a minimal scenario that produces stakeholder-ready artifacts — and iterate.
  • •Shaping call: define outcomes, constraints, and evidence sources
  • •Draft outputs: what the customer will receive at Consider/Architect
  • •Validation plan: how we prove success at Validate
  • •Packaging: artifact bundle + journey tracking
Entrance fee (scenario development)
Custom scenarios have an entrance fee for rapid engineering, validation of the artifact model, and safe delivery packaging.
What the entrance fee includes
  • •Scenario definition + success criteria
  • •Artifact bundle blueprint (what you’ll get at each stage)
  • •Security + delivery constraints (client-side first)
  • •Initial implementation + demo-ready preview
What we need from you
We don’t need secrets upfront. We need clarity: what “done” means, your evidence sources, and your constraints.
  • •Target outcome (risk reduction, cost reduction, reliability, compliance)
  • •Scope boundaries (tenants, subscriptions, regions, workloads)
  • •Constraints (change windows, governance, access methods)
  • •Evidence sources (logs/exports/screenshots) or live assessment methods
  • •Stakeholders and who can approve/execute
Request a scenario (RFS)
Use the portal RFS form to describe what you want. We’ll respond with feasibility, entrance-fee scope, and what a portal preview (and any trial allowance) looks like.
Open RFS form →Talk to MSC →
We can craft scenarios across vendors/platforms — the constant is the MSC loop: Consider → Architect → Validate → Amplify.
⟐⌁◈⌂✦★✎⛨
Page 9 - Virtual MSC Appliance on Azure Local (IaC)

Keep the work inside your perimeter

Run MSC inside your perimeter with the Azure Local appliance — offline/air‑gapped if needed.
In regulated, air-gapped, or sovereignty-sensitive environments, “nice SaaS” isn’t a plan. MSC supports digital sovereignty by offering an on‑premises deployment model: the MSC Azure Local appliance.
What “digital sovereignty” means here
It’s not marketing — it’s a delivery constraint: evidence, artifacts, and operational metadata must remain under customer ownership and within approved locations.
  • •Data residency and geographic controls are first-class inputs
  • •Evidence defensibility (holds/retention) is treated as part of the design
  • •No requirement for inbound public exposure
MSC Azure Local appliance
A self-contained virtual appliance that packages the MSC platform so you can run the portal and its scenario engine inside your environment.
  • •Runs on Azure Local (Azure Stack HCI), Hyper‑V, or VMware
  • •Supports fully offline operation after deployment
  • •Updates can be applied via imported scenario packages (USB/offline workflow)
What customers gain
The same MSC “evidence-first” loop — delivered in a way that fits strict security postures.
  • •Shared multi-user portal inside your internal DNS
  • •Local artifact/evidence storage under your controls
  • •Operational cadence without cloud dependency
Deployment snapshot
Typical deployment is a VM on your chosen platform with HTTPS for the portal and an admin console. Internet access is optional; in air‑gapped mode, updates are applied offline.
Default access
Portal: 443 · Admin: 8443 · SSH: 22
Sizing (typical)
4 vCPU · 8 GB RAM · 100 GB disk (recommended)
See appliance architecture →Talk to MSC →
Note: this public portal deployment is cloud-hosted. The appliance is for customers who require on‑premises control.
⟐⌁◈⌂✦★✎⛨
2026 LuiT || ₷©®•Modern Support Consult•Hosted on Microsoft Azure + GitHub Enterprise
FAQPrivacyTermsAccessibilitySecuritySupportTRIX
Support details(version & routing)
APImsc-portal-api-d7g5fudfa7eufufa.westeurope-01.azurewebsites.net
Build6d394df1@20260501T180220Z
Billing & licensing(public summary)
This portal provides structured assessments and actionable guidance. Results depend on what is observable and what changes are implemented in your environment.
Results depend on inputs
  • Online scenarios measure available signals (for example: public DNS records) and report what is observable at the time of the run.
  • Guidance describes recommended steps; applying them may require configuration changes, permissions, vendor behavior, and timing.
  • Outcomes are influenced by multiple moving parts; we focus on measurable improvements, defensible choices, and clear evidence you can act on.
How costs are calculated (customer view)
  • Online run pricing: charged per paid online run. The price shown at checkout for the selected scenario is the source of truth.
  • Customization-supported scenarios: scope and pricing are confirmed with you (in writing) before work begins, and only change if scope assumptions materially change.
  • Performance-aligned pricing (larger scenarios): for eligible, explicitly agreed engagements, a portion of pricing can be aligned to measured outcomes. Where used, the percentage applied by MSC/LuiT is fixed (currently 3.69%) and is applied only after the model is understood, resonates, and is explicitly approved.
  • Billing cadence & crediting: billing can be issued monthly for the agreed delivery window, followed by a success reconciliation/credit once outcomes are verified against the agreed deliverables.
  • Taxes (such as VAT) may apply depending on your location and billing details. Invoice/checkout totals are the source of truth.
Fairness & exceptions
Reconciliation is based on the agreed deliverables and the available inputs. If customer-side deliverables (access, approvals, change windows) are delayed after being identified as blockers, we may pause measurement or re-baseline the delivery window. We prefer fast, transparent review and adjust when the facts support it.
License scope
Some scenarios and deeper artifacts are intentionally restricted in public mode. For customization-supported engagements, licensing/procurement and exact deliverables are confirmed before work begins. If you need enterprise-wide terms or invoicing, use Support.
Why Modern Support Consult
Microsoft-first, on-prem friendly
MSC is built around Microsoft infrastructure and cloud operations, with on-premises realities treated as first-class. Built by an Exchange-focused specialist (~30 years IT; ~20 years Microsoft messaging & integration).
Curated, regulated guidance
Not random tips: curated and cross-compared to reduce noise and keep actions defensible.
Benchmarking + checklist outputs
Scenarios benchmark posture and produce checklist-style remediation aligned with mainstream security/ops methods.
Quadral method (Codex / Metaflow-ready)
Evidence → traceable outcomes: signals, checks, decisions, guidance, exceptions. Designed for consistent benchmarking and audit-friendly reasoning.