FAQ

Quick answers about the journey and how to use the portal.

Quick answers about MSC, the 4-stage journey, and what the portal does (and does not) do automatically.
Back to portal
Quick links
FAQ
Common questions
Support
Ask Fop
RFS
Request a scenario
Security
Report concerns
Privacy
Data handling
Terms
Usage conditions
Accessibility
Feedback channel
Quick links: What is MSC? · What are the 4 journey stages? · What is Metaflow intel (and what does “Transcendant” mean)? · What does the Amplify stage actually mean? · Does MSC execute changes for us? · How do I contact support?
What is MSC?

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.

What are the 4 journey stages?
  • 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.
What is Metaflow intel (and what does “Transcendant” mean)?

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.

What does the Amplify stage actually mean?

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.

Does MSC execute changes for us?

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.

How do I contact support?

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

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.