MSC (Modern Support Consult) is a structured, evidence-first way to assess, plan, validate, and scale IT outcomes — without surprise automation. The portal helps you produce clear, customer-safe outputs (reports, decision notes, checklists, exportable artifacts) that your IT team can execute on.

Most scenarios focus on Microsoft infrastructure and cloud operations (security, identity, messaging, integrations, and day-2 operations), where “what to do next” is often less important than proving why.

This portal is published as a SaaS offer in the Microsoft Commercial Marketplace. Microsoft is the merchant of record: Microsoft handles billing, taxes, invoices, refunds, plan changes, and cancellation under your Microsoft Customer Agreement and the Marketplace terms you accepted at subscribe time.

Manage the subscription from Azure Portal → SaaS subscriptions in the tenant that owns it. MSC support handles product behavior and technical questions, but cannot adjust Microsoft invoices.

You can run the E-mail Security Snapshot without a subscription and download its result without a separate Amplify charge. You can also explore a Messaging Assessment Generator configuration before subscribing. Starting an Architect run requires an active subscription and an available journey; Jump Drive is not required for MSC-hosted Messaging results. Supported evidence may include reviewed readings and examples clearly marked as mock. Original-file uploads are not available for Architect runs yet. Check the availability shown for your scenario before submitting information.

You can also prepare configuration for other scenarios before subscribing. The portal shows when a customer workspace, a subscription, or a separately accepted Amplify gain-share is required before your next run.

Your Marketplace subscription gives you access to eligible scenario stages. Before an Amplify run, you review and separately accept the gain-share calculated for that scenario and journey. The portal shows the calculation and any permitted adjustment before you accept it.

An accepted Amplify position does not pay for another scenario or a new Messaging Assessment Generator configuration. You can review that new scope and its own gain-share before deciding whether to continue.

In a new browser, enter the billing email used for your Marketplace subscription and select Verify now. The portal checks the subscription and sends a one-time recovery code to that address. Enter the code in the same panel to reopen your latest purchased journey(s); other recovered journeys remain available in that panel.

Your accepted Messaging configuration stays fixed, while a separate new assessment remains editable. Recovery works after clearing browser data or switching browsers. An older journey that cannot be linked to your purchase still needs its original access link.

Your restored workspace shows your saved planning configuration, but does not replay earlier evidence uploads, extracted readings, or validation notes in the recovery view. Recovery does not delete the evidence or generated assessment files already in your workspace. If a restored assessment needs evidence, you can review it and upload it again; new validations can be recorded without replacing your earlier work.

Yes. Open your restored journey and select Add scenario to this journey. The new run stays in the same journey, so its saved context can support a follow-up assessment. Select New journey only when you want to start separately.

The E-mail Security Snapshot remains free. Other scenarios check their own subscription and Amplify requirements; an acceptance for one scenario does not unlock another. Runs added under your verified account appear when you restore the journey in another browser. Older free runs without verified account ownership remain separate.

Yes. In the portal, confirm deletion of the selected journey to remove its saved assessments, generated files, and workspace. A Messaging assessment can also be deleted individually without removing the other runs in its journey.

From a new browser, verify your billing email first; you can delete a purchased journey when all its runs belong to your account. Deletion does not cancel or refund a settled purchase. Required payment and audit records remain; a deleted journey cannot be restored from its old Amplify acceptance.

When a scenario supports evidence uploads, files are sent directly from your browser to your designated storage workspace. The portal keeps the references and assessment context needed to build your report. Restoring a purchased journey does not copy your uploaded files or extracted readings into the recovered view, and does not delete existing evidence or generated files from your workspace. You can upload evidence again when continuing a restored assessment.

Generated output files created for your request, together with operational metadata such as request identifiers, run status, and timestamps, follow the retention windows in the Data Processing Agreement.

• Consider: collect signals, constraints, and a baseline.
• Architect: design the approach and draft the plan (including change candidates).
• Validate: test the plan, confirm readiness, and validate proposed changes.
• Amplify: scale and operationalize outcomes with your internal IT team owning RFCs and execution.

Metaflow intel is MSC’s way of turning messy reality into defensible next steps. It keeps a simple chain of reasoning visible: signals → hypotheses → checks → decisions → next actions.

Transcendant (⑦) is a visual shorthand for coherence: when intent, architecture, validation, and amplification align, you get higher confidence per change and less friction in execution. It’s not “magic”—it’s a label for momentum that comes from aligned evidence.

Amplify is about strengthening your IT team: turning validated recommendations into repeatable execution. This is where change requests (RFCs), rollout waves, communications, runbooks, and operational ownership live.

The portal supports the work with structured evidence, tracking artifacts, and guidance — but it does not automatically perform tenant-wide changes.

Not automatically. By default, changes/RFCs are driven and executed by your internal IT staff. MSC provides the framework, evidence, and the “why/what/how” so your team can apply changes safely (often with scripts, checklists, and rollback notes).

If you want MSC to perform change execution, that requires a customized assisted consultancy engagement with explicitly agreed scope, access methods, and change windows.

Use the Support page for contact details and what to include when you reach out.Open Support.