ISV BACKEND · LINKING
IT consulting, illuminated.Modern Support Consult turns Microsoft change into a sharp, evidence-led delivery path.
Modern Support Consult
Desktop noticeSignal lane

MSC is a Windows desktop app for IT professionals. Use it on a desktop or laptop device. Mobile access is limited to 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
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.
FREE Messaging Assessment Generator configuration→FREE E-mail Security Snapshot → DNS report→Deliver Plan de Campagne
Signal feed
live
What took hours → now takes minutes
Open portal — Start here
Preview tour
to see if we understand why you arrived on our MSC Portal?
Available on Microsoft MarketplaceAvailable on Microsoft Marketplace

Jump Drive connects your Azure Blob workspace for eligible journeys. A connection check does not deliver results or unlock a scenario. Check availability in the portal before starting your next stage.

⟐⌁◈⌂✦★✎⛨
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.

Jump Drive connects your Azure Blob workspace for eligible journeys. A connection check does not deliver results or unlock a scenario. Check availability in the portal before starting your next stage.

⟐⌁◈⌂✦★✎⛨
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.
Winsight indicator levels
Each artifact carries the same indicator scale. Transcendant flags a finding that keeps returning across runs; Sovereign flags a chance to strengthen residency, retention, or evidence ownership.
  • CriticalEvidence supports acting now.
  • ElevatedPlan this into the near-term work.
  • ModerateSchedule alongside planned change.
  • LowKeep watching; no action required yet.
  • InfoContext for the record; nothing to action.
  • TranscendantRecognised across runs — treat as a roadmap pattern, not a one-off.
  • SovereignOpportunity to strengthen data residency, retention, or evidence ownership.
Mail securityLock protection
Demo scenario · Architect
Exchange Server Design
Architect-stage global architecture: projected role topology, storage model, security baseline, and bill of materials.
Projected sizing tablesBill of materialsWinsight indicator rail
Open artifacts →
Microsoft DefenderExchange access
Demo scenario · Architect
Messaging Security Remediation Roadmap
Amplify-stage operations HLD: target authentication architecture with the change manifest hand-off.
Real chapter structureChange manifestWinsight indicator rail
Open artifacts →
Demo scenario · Architect
Optimize Outlook
Validate-stage scoring dashboard: score domains against the profile baseline, with evidence state per client.
Six scoring domainsBaseline comparisonWinsight indicator rail
Open artifacts →

Jump Drive connects your Azure Blob workspace for eligible journeys. A connection check does not deliver results or unlock a scenario. Check availability in the portal before starting your next stage.

⟐⌁◈⌂✦★✎⛨
Page 4 · Business model

Start with a free baseline. Prepare the next stage when it is available.

E-mail Security Snapshot is free to run; Messaging Assessment Generator configuration is free to prepare. An Architect run requires an active subscription and an available stage; Amplify needs separate acceptance.
Free entry: You can prepare a Messaging Assessment Generator configuration. E-mail Security Snapshot runs free through Validate and its DNS posture report is downloadable. A Generator Architect run needs an active subscription when available.

Level 2+ subscription: Prepare configuration without an active subscription. When offered, EUR 7/month supports eligible Architect planning after the stage prerequisites are met.

Amplify gain-share: Entry to Amplify requires explicit customer acceptance of 1,369% gain-share of financial outcomes.

Downloads and full cycling: Availability, result access, and any Amplify acceptance are checked for each stage; no payment or workspace setup silently authorizes a run.

Beyond baseline: Resource overage is a future plan option, not an active meter in this offer.
Transparent pricing aligned with your success
Activation map
A compact view of what’s free vs what triggers activation.
FreeActivationPromo exception
MSC subscription model diagramThe Messaging Assessment Generator can be configured before subscribing; its Architect run needs an active subscription and an available journey. The E-mail Security Snapshot is free to run and download. The monthly subscription supports eligible Level 2 and higher journeys, subject to stage readiness. Amplify requires a separate acceptance.When offered: EUR 7/month planningMessaging Assessment Generatorfree configurationE-mail Security SnapshotValidate + downloadLEVEL 3+ JOURNEYSsubject to workspace readinessAmplifyexplicitly accept 1,369% gain-shareFull scenario cyclingAmplify state + downloadable artifactsUnlocked only after explicit Amplify acceptanceFree preparation or a free Snapshot baselineStage runs depend on current availability and required acceptance
Free ways to start
Prepare a Messaging Assessment Generator configuration at no charge. E-mail Security Snapshot is free to run and download, with no Amplify stage.
Level 3+ planning
Prepare configuration first. When available, EUR 7/month supports eligible planning, but does not bypass workspace readiness.
Amplify gain-share
Move to Amplify only when you choose execution-ready delivery and explicitly accept the 1.369% gain-share.
Azure resource metering
A future resource-overage option is not an active charge in the current plan. Review the applicable offer terms before subscribing.

Jump Drive connects your Azure Blob workspace for eligible journeys. A connection check does not deliver results or unlock a scenario. Check availability in the portal before starting your next stage.

⟐⌁◈⌂✦★✎⛨
Page 5 · Deployment model value

Secure by design: transparent controls, trusted boundaries, and customer-owned outcomes

No embedded administrator secrets, clear assessment records, and control over where your evidence is stored.
Your browser connects to the portal service without embedded administrator secrets. Where uploads are supported, your evidence goes to your designated workspace; run context and generated results follow the applicable retention rules. If you reopen a purchased journey in a new browser, you can recover planning settings without copying earlier uploads or extracted readings into the restored view.
Explore our security approach →Leveraging MSC Appliance →No administrator secrets in the portal • Defined retention • Customer-controlled evidence
One-line promise
Restoring a journey does not copy previously uploaded evidence.
Restoring planning settings does not deliver new files or remove previously delivered files from your workspace.
Trust boundary (at a glance)
Your browser sends assessment requests to the public API. Where a released journey accepts uploads, evidence goes to your designated workspace.
Browser access
Browser
Your portal view
→
Public API
Assessment requests
→
Customer storage
Your Azure Blob workspace, when eligible
Assessment records
We retain run context and generated results under the applicable retention rules. Recovery does not make a second copy of your uploads.
Runs client-side
Use the portal in your browser without entering administrator credentials.
  • ✓Your portal view works in a standard browser
  • ✓Your browser sends assessment requests through the portal service
  • ✓No administrator secrets are embedded in the portal
Audit + governance friendly
Deterministic artifact bundles with journey IDs—easy to review, easy to sign off.
  • •Least-privilege design with no hidden dependency on super-admin access
  • •Clear provenance through journey IDs, metadata, and repeatable outputs
  • •Bring-your-own workspace for retention, approvals, and policy alignment
Customer-owned destinations
Protected artifact delivery to customer-owned Azure Blob storage is available only for released journeys.
  • •Azure Blob containers in your storage account are the supported destination
  • •Connecting a workspace checks access; it does not deliver a result
  • •MSC retains run records separately under the applicable retention terms
Assessment records and recovery

When you verify a purchased journey in another browser, your saved planning configuration is available again. The restored view does not replay earlier evidence uploads, extracted readings, or validation notes. Your existing workspace and generated files are unchanged; you can review your released journey's available inputs and record new validations without replacing earlier work.

Recorded for your assessment
  • •Journey IDs, status, and operational metadata
  • •Assessment context and generated results, under applicable retention rules
  • •References to evidence in your designated workspace
Not copied into recovery
  • •Uploaded evidence files
  • •Extracted readings and earlier validation notes
  • •Generated assessment file bodies

Jump Drive connects your Azure Blob workspace for eligible journeys. A connection check does not deliver results or unlock a scenario. Check availability in the portal before starting your next stage.

⟐⌁◈⌂✦★✎⛨
Page 6 · The Portal Surfaces

Three panels, one narrative

Winsight reviews the evidence from four angles. Journeye reads the journey-wide direction and holds the governance boundary. Operandum steers emphasis without touching authorization.

Abstract. Winsight Engine

Winsight

Metaflow Insight · Evidence-first intel

Decisions
12
Candidates
7
Guidances
4
Waivers
2
Intel Trail
23
Signals
156
Activity
8
Four-angle evidence review

A balanced view of the evidence behind this assessment.

Strategy78%
Tactics64%
Analysis71%
Likelihood59%
Overall68%
Strategic · Tactical · Analytical · Likelihood intel
Hover an area to reveal its third-layer detail panel.

Journeye

Travelore · PortflowIO

Travelore

Journey progress from the user view — Travelore lens (per journey).

Scenario efficiency
100%
Completed scenarios3 of 3 complete · 100%
Gain burst
3 scenarios started
Estimated customer time-value gain€ 15.818
Messaging Scenario Generator€ 355
Messaging Security Remediation Roadmap€ 13.722
Email Security Snapshot€ 1.741
Messaging Scenario Generator€ 355
Messaging Security Remediation Roadmap€ 13.722
Email Security Snapshot€ 1.741
Projection based on the current scenario scope and progress
Amplified scenarios: Security Roadmap
Consider
Architect
Validate
Amplify
Journey-wide pattern direction

A calendar-informed focus translated into practical assessment language.

Assessment focus
Confirm measured evidence before promotion
Operating direction
Consolidate what is already proven
Evidence rationale
  • Evidence coverage is broad enough to read a direction.
  • Analysis is the strongest angle in this journey.
Evidence stewardship
82%
9 of 11 evidence signals considered
Decision direction
100%
Evidence informs; your team decides.
Control boundary
Customer governed
You retain evidence, approvals, and delivery authority.
Keeps stage, runs, and decisions reviewable
Artifact selection stays on the workflow surface that owns it.

Operandum

Optional customer profile. Helps tailor wording, outputs, and engagement posture.

Project management methodologies
PRINCE2ScrumKanban
IT delivery style
DevOpsWaterfallAgile (iterative)Hybrid delivery modelContinuous Delivery
Adopted architecture framework
TOGAFZachmanMicrosoft CAF
Infrastructure management platforms
Microsoft Configuration Manager (MECM)Microsoft IntuneVMware Workspace ONE UEMIvanti Neurons for UEMHCL BigFix
Stored locally in this browser. When a journey is linked, your profile syncs to the MSC workspace. You can leave everything blank.

Jump Drive connects your Azure Blob workspace for eligible journeys. A connection check does not deliver results or unlock a scenario. Check availability in the portal before starting your next stage.

⟐⌁◈⌂✦★✎⛨
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.

Jump Drive connects your Azure Blob workspace for eligible journeys. A connection check does not deliver results or unlock a scenario. Check availability in the portal before starting your next stage.

⟐⌁◈⌂✦★✎⛨
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
Scenario development fee
A custom scenario is built work, so it is quoted separately from the portal subscription. The fee covers rapid engineering, validation of the artifact model, and safe delivery packaging. Your €7,00/month subscription and the Amplify gain-share terms are unchanged.
What the development 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: Architect → Amplify → Validate → Consider.

Jump Drive connects your Azure Blob workspace for eligible journeys. A connection check does not deliver results or unlock a scenario. Check availability in the portal before starting your next stage.

⟐⌁◈⌂✦★✎⛨
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
  • •Winsight raises a Sovereign indicator when a run finds a way to strengthen residency, retention, or evidence ownership
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.

Jump Drive connects your Azure Blob workspace for eligible journeys. A connection check does not deliver results or unlock a scenario. Check availability in the portal before starting your next stage.

⟐⌁◈⌂✦★✎⛨
2026 LuiT || ₷©®•Modern Support Consult•Hosted on Microsoft Azure
FAQSupportArchitectureRFSSecurityPrivacyTermsAccessibilityPartnersLegal
Support details(version & routing)
APImsc-portal-api-d7g5fudfa7eufufa.westeurope-01.azurewebsites.net
Build00307dbb@20261113T142220Z
LaneMicrosoft Commercial Marketplace (ISV Success)
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)
  • Microsoft Commercial Marketplace: Microsoft is the merchant of record. Microsoft handles billing, taxes, invoicing, refunds, plan changes, and cancellation under your Microsoft Customer Agreement. Manage the subscription from Azure Portal → SaaS subscriptions.
  • Plans & metering: per-plan price and any metered dimensions are visible in the Marketplace offer at checkout. Charges appear on your Microsoft invoice.
  • Customization-supported scenarios: scope and pricing are confirmed with you (in writing) before work begins, and only change if scope assumptions materially change.
  • Taxes are calculated and collected by Microsoft. Marketplace invoices 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.

Who is behind MSC

MSC is developed and owned by N.v.Luijtelaar, who builds and supports the platform. Background: Microsoft Certified Master | Exchange Server.

Use Close to return to the portal.