Defense & Intelligence · Managed platform (Microsoft 365)

DoD IL6 "Secret" Cloud Collaboration

Microsoft 365 at the Secret level, administered by cleared Moraph staff under your authority

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

Moraph helps defense organizations bring Microsoft 365 email and Teams into use in Microsoft's US government Secret cloud, and then administers the environment as a managed service. Administration is carried out by Moraph staff who are US citizens holding active clearances, working only under the access, facilities and procedures your organization authorizes. Authorization decisions, classification decisions and the platform itself stay with your authorizing official, your users and Microsoft respectively.

The problem it solves

Commercial collaboration tools are available at the Secret level, but standing them up and running them is a different job from running them on unclassified networks. Configuration has to follow the security requirements of a classified environment, every change has to go through your authorization process, and the people who administer the tenant must hold the right clearances and qualifications. Many organizations have the requirement and the licences but not enough cleared, qualified administrators to run the environment day to day.

  • Cleared administrators with Microsoft 365 experience are hard to recruit and retain
  • Configuration must be documented and kept in line with the approved baseline
  • Every change needs to pass through the organization's change and authorization process
  • Monitoring, access reviews and incident support must happen within classified procedures

Who uses it

  • DoD components and commands adopting Microsoft 365 at the Secret level
  • Command IT leads and program offices who own the collaboration service
  • Information system security managers and officers responsible for the environment
  • Authorizing officials' staff who need evidence of how the environment is run
  • Defense agencies supplementing their own cleared administration teams

Requirements it supports

DoD Cloud Computing Security Requirements Guide (CC SRG)DoDI 8510.01, Risk Management Framework for DoD SystemsCNSSI 1253, Security Categorization and Control Selection for National Security SystemsDoDM 5200.01, DoD Information Security ProgramDoDM 8140.03, Cyberspace Workforce Qualification and Management Program32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM)

The product supports these requirements; meeting them remains your organization’s responsibility.

Responsibilities

Who is responsible for what

Microsoft provides the platform, Moraph administers it within the access your organization grants, and your organization keeps every authorization, security and policy decision.

AreaMoraphMicrosoftYour organization
LicensingTracks licence counts and assignments and advises on what is neededProvides licences under its terms and your contract vehiclePurchases licences and approves changes in quantity
Platform availabilityTracks service notices and coordinates with Microsoft supportOperates the cloud service and its infrastructure under its own commitmentsProvides network connectivity and end-user devices
AuthorizationPrepares configuration and operational evidence for your packageMaintains the platform's own authorization with DoDIssues and maintains the authority to operate for your use
Tenant configurationConfigures and maintains the tenant against the approved baselineProvides the configuration options available in that cloudApproves the baseline and any changes to it
Identity and accessAdministers accounts and groups as requested; prepares access reviewsProvides the identity and access capabilities of the platformIssues credentials, grants administrative access and certifies reviews
Monitoring and incident responseTriages routed alerts and supports incidents as directedMonitors and responds to incidents in its own infrastructureRuns security operations, directs incident response and reports incidents
ChangesPrepares change requests and implements approved changesAnnounces platform changes through its service noticesApproves or rejects every change through its change process
Platform updatesReviews Microsoft's announced changes and assesses their effect on the baselineDevelops, tests and releases updates to the platformDecides how to respond where an update affects the baseline
Classification and contentDoes not classify, mark or review content except as directed for a taskHosts content in the platformUsers and classification authorities classify, mark and handle content
User supportHandles requests and second-line issues raised through your processProvides platform support to Moraph and your organization under its termsProvides first-line support and end-user training

See how it works

A short walkthrough

Illustrative screens of how Moraph runs the service, with fictional sample data. They are not screens of M365 itself, which belongs to its vendor.

  1. Step 1

    The onboarding tracker

    Onboarding is tracked unit by unit, with what is complete and what is waiting on whom.

    UnitUsersEmailTeamsWaiting onStatus
    Example Unit A (fictional)120DoneDoneNoneLive
    Example Unit B (fictional)85DoneIn progressMoraphIn progress
    Example Unit C (fictional)210PlannedPlannedSite credentialsWaiting
    Example Unit D (fictional)40PlannedPlannedSchedulingPlanned
    Onboarding is tracked unit by unit, with what is complete and what is waiting on whom.

  2. Step 2

    The baseline check

    Moraph checks the tenant against the approved baseline and reports any drift to your security staff.

    Baseline check BC-014 · Example Command (fictional)

    Baseline version
    v7 (approved)
    Settings checked
    312
    Matching
    309
    Drift found
    3
    Checked by
    Moraph administrator

    Drift found

    • !External meeting access setting differs from baseline
    • Mailbox audit setting on two new mailboxes not applied
    • Guest access remains disabled, as approved
    Moraph checks the tenant against the approved baseline and reports any drift to your security staff.

  3. Step 3

    Change requests

    Every change outside the baseline is prepared by Moraph and approved through your process before it is made.

    ChangeSummarySecurity-relevantApproverStatus
    CR-0231Correct external meeting access settingYesISSMAwaiting approval
    CR-0229New shared mailbox policy for Unit BNoService ownerApproved
    CR-0226Retention label for operational recordsYesISSMImplemented
    CR-0222Teams naming policy updateNoService ownerRejected
    Every change outside the baseline is prepared by Moraph and approved through your process before it is made.

  4. Step 4

    Alert triage

    Alerts your organization routes to Moraph are triaged and passed on with context, and your security staff direct the response.

    Alert AL-0587 · Unusual administrative sign-in (sample)

    1. Alert received from platformPlatform
    2. Sign-in matched to approved change windowMoraph administrator
    3. Context added and passed to security operationsMoraph administrator
    4. Activity confirmed as expectedSecurity operations
    5. Alert closed with noteISSM
    Alerts your organization routes to Moraph are triaged and passed on with context, and your security staff direct the response.

  5. Step 5

    The access review

    Administrative access is reviewed on the agreed cycle, and your ISSM certifies each decision.

    Role holderOrganizationPlatform roleGranted byDecision
    Administrator 1 (fictional)MoraphExchange administratorISSMKeep
    Administrator 2 (fictional)MoraphTeams administratorISSMKeep
    Administrator 3 (fictional)MoraphGlobal readerISSMRemove: role no longer needed
    Local admin 1 (fictional)Your organizationUser administratorISSMKeep
    Administrative access is reviewed on the agreed cycle, and your ISSM certifies each decision.

  6. Step 6

    The service review

    Moraph's service manager reviews the period with your program office and security staff, and agreed actions are tracked.

    Service review · Example Command (fictional) · Sample period

    Requests completed
    146
    Requests open
    12
    Changes implemented
    5
    Changes awaiting approval
    1
    Alerts triaged
    23
    Microsoft service notices
    4

    Actions agreed

    • Approve or reject CR-0231 (ISSM)
    • Confirm Unit C site credentials (Site IT lead)
    • Assess announced Teams change against baseline (Moraph)
    Moraph's service manager reviews the period with your program office and security staff, and agreed actions are tracked.

Workflows

The principal workflows

  1. Onboard

    Moraph works with your program office, security staff and Microsoft to bring your organization into use on the platform, following the steps your authorization process requires.

    • Scope agreed: units, users, workloads and the approved configuration baseline
    • Moraph administrators' clearances and qualifications verified by your security office
    • Administrative access issued by your organization under its own procedures
    • Tenant configured against the baseline and the evidence recorded for your security staff
    • Units and users brought on in the order you choose

  2. Administer

    Day-to-day administration of email, Teams, users, groups and policies is carried out by cleared Moraph staff, within the permissions your organization grants.

    • Service requests received through your ticketing process
    • Requests within the approved baseline completed by a Moraph administrator
    • Each action recorded against the ticket and in the platform's audit log
    • Requests outside the baseline raised as change requests
    • Users and requesters told when work is complete

  3. Change

    Configuration changes follow your change and authorization process. Moraph prepares the request and its security impact notes, and implements only what your organization approves.

    • Change request prepared with purpose, configuration detail and rollback plan
    • Security impact notes prepared for your ISSM
    • Your change board and security staff approve or reject the change
    • Approved change implemented in the agreed window and verified
    • Configuration baseline and evidence updated

  4. Monitor and review

    Moraph watches service health and the alerts your organization routes to it, supports your security staff on incidents, and reviews the service with you on a regular cycle.

    • Platform health and service notices from Microsoft tracked
    • Alerts triaged and passed to your security operations or CSSP as your procedures set
    • Incidents supported under the direction of your security staff
    • Administrative access reviewed with your ISSM on the agreed cycle
    • Service review held with your program office

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Service owner

Command IT lead, program manager, collaboration service owner

Owns the collaboration service for your organization and decides what Moraph works on.

Sees

  • Service reports on requests, changes, alerts and reviews
  • Change requests and their approval status
  • Licence counts and assignments
  • Microsoft service notices that affect the environment

Does

  • Approves the scope of the service and its priorities
  • Chairs or attends service reviews
  • Approves changes that affect users or service scope
  • Decides which units and users are brought on, and when
  • Escalates service concerns to Moraph's service manager

Cannot

  • Approve security-relevant changes in place of the ISSM
  • Grant administrative access outside your organization's procedures
Approvals
Approves service scope and user-affecting changes; security-relevant changes also need the ISSM's approval.
Notified about
Change requests waiting for their decision, service reviews, and Microsoft service notices affecting users.

ISSM or ISSO

Information system security manager, information system security officer

Responsible for the security of the environment within your authorization, and directs Moraph's security-relevant work.

Sees

  • The configuration baseline and any drift found
  • Change requests with their security impact notes
  • Administrative access lists and review results
  • Alerts and incident records routed through Moraph

Does

  • Approves or rejects security-relevant changes
  • Verifies Moraph administrators' clearances and qualifications with your security office
  • Certifies administrative access reviews
  • Directs incident response actions
  • Uses Moraph's evidence in your authorization package

Cannot

  • Have Moraph accept risk or make authorization decisions on your organization's behalf
  • Edit Moraph's change and service records after they are closed
Approvals
Approves security-relevant changes and access reviews; authorization decisions rest with your authorizing official.
Notified about
Security-relevant change requests, configuration drift, alerts escalated by Moraph and access reviews due.

Moraph cleared administrator

Microsoft 365 administrator, messaging administrator, Teams administrator

Carries out the administration of the tenant within the access and procedures your organization grants.

Sees

  • The tenant's configuration and administrative portals, within the roles assigned to them
  • Requests and change requests assigned to them
  • Alerts routed to Moraph by your organization

Does

  • Completes service requests within the approved baseline
  • Prepares change requests and security impact notes
  • Implements approved changes and verifies them
  • Triages alerts and passes them on with context
  • Supports incidents as directed by your security staff
  • Prepares access review and baseline check evidence

Cannot

  • Make changes outside the approved baseline without an approved change request
  • Grant themselves or other Moraph staff additional access
  • Read message or file content except as directed for a specific task by your organization
  • Work from facilities or networks your organization has not approved
Approvals
All changes outside the baseline are approved through your change process; their access is granted and reviewed by your organization.
Notified about
New requests and changes assigned to them, approved change windows and alerts routed to Moraph.

Moraph service manager

Service delivery manager, engagement lead

Runs the managed service day to day and is accountable to your service owner for how it is delivered.

Sees

  • All requests, changes and alerts handled by Moraph
  • Staffing and clearance status of the Moraph team assigned to you
  • Service reports and review actions

Does

  • Assigns work to Moraph administrators
  • Prepares and leads service reviews
  • Tracks actions from reviews to completion
  • Coordinates with Microsoft support on platform issues
  • Escalates issues within Moraph and to your service owner

Cannot

  • Approve changes on your organization's behalf
  • Change administrative access in the tenant
  • Commit your organization to licence purchases
Approvals
Scope changes they propose are approved by your service owner.
Notified about
Requests approaching the targets agreed in the service description, escalated alerts, and Microsoft service notices.

Site IT lead

Unit or site IT lead, local administrator, help desk lead

Represents a unit or site, raises requests for its users and confirms when work is done.

Sees

  • Requests they or their site raised
  • Service notices affecting their users
  • Onboarding status for their unit

Does

  • Raises requests for accounts, groups, mailboxes and teams
  • Confirms completed work or reopens it
  • Supports their users with first-line questions
  • Takes part in onboarding for their unit

Cannot

  • Approve changes to the tenant configuration
  • See other sites' requests or users
Approvals
Requests that change policy or configuration go to the service owner and ISSM.
Notified about
Updates on their requests and service notices affecting their users.

Assessor (read-only)

Security control assessor, auditor, inspector general staff

Reviews how the environment is run, using Moraph's records, without being able to change them.

Sees

  • The configuration baseline and baseline check results
  • Change records with approvals
  • Access review results
  • Service reports

Does

  • Reads and exports records within the scope granted
  • Requests additional evidence through the ISSM

Cannot

  • Change, approve or close anything
  • Keep access after it expires
Approvals
Their access is approved by your ISSM, with a scope and an end date.
Notified about
Nothing by default; access granted and expiring is confirmed to the ISSM.

Authorizing official's representative

AO designated representative, cybersecurity risk staff

Receives evidence of how the environment is run to support the authorizing official's decisions.

Sees

  • Evidence packages prepared for your authorization
  • Significant changes and their security impact notes
  • Open findings and their status

Does

  • Reviews evidence and significant changes
  • Requests further evidence through the ISSM
  • Records decisions in your organization's own systems

Cannot

  • Delegate authorization decisions to Moraph
  • Change Moraph's records
Approvals
Authorization decisions are made by your authorizing official under your organization's process.
Notified about
Significant changes and evidence packages, as the ISSM routes them.

Permissions at a glance

ActionService ownerISSM/ISSOMoraph adminService mgrSite IT leadAssessorAO rep
Raise service requestsFullFullNo accessFullOwn work onlyNo accessNo access
Complete requests within baselineNo accessView onlyFullView onlyView onlyNo accessNo access
Prepare change requestsFullFullFullFullNo accessNo accessNo access
Approve security-relevant changesView onlyApprovesNo accessView onlyNo accessView onlyView only
Approve user-affecting changesApprovesApprovesNo accessView onlyNo accessNo accessNo access
Implement approved changesNo accessView onlyFullView onlyNo accessView onlyNo access
Grant administrative accessNo accessApprovesNo accessNo accessNo accessNo accessNo access
Certify access reviewsView onlyApprovesNo accessView onlyNo accessView onlyView only
Triage alertsNo accessView onlyFullView onlyNo accessNo accessNo access
Direct incident responseView onlyFullNo accessView onlyNo accessNo accessView only
View baseline and change recordsView onlyView onlyView onlyView onlyNo accessView onlyView only
Approve service scopeApprovesView onlyNo accessView onlyNo accessNo accessNo access
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Moraph administrators hold only the platform roles your organization assigns them, and those roles are granted, reviewed and removed under your procedures, not Moraph's.
  • Security-relevant changes always need your ISSM's approval, and Moraph never approves its own changes. Authorization decisions remain with your authorizing official.
  • Every Moraph action is recorded against a request or change and appears in the platform's own audit log, so both records can be compared during assessment.
  • Federal and defense work, including every ticket for this service, is handled only by Moraph staff who are US citizens with active clearances, working from facilities and networks your organization approves.

Features

What it does

Cleared administration

Administration carried out by Moraph staff who are US citizens with active clearances at the level your organization requires, verified by your security office.

Classified email

Exchange Online, as available in Microsoft's Secret cloud, configured for your mailboxes, distribution groups, transport rules and retention.

Teams chat and meetings

Microsoft Teams, as available in that cloud, configured with the team, channel, meeting and external access policies your organization approves.

Configuration baseline

The approved tenant configuration documented as a baseline, checked by Moraph on a regular cycle, with any drift reported to your security staff.

Change management

Every configuration change prepared, approved through your process, implemented and verified, with the record kept for your authorization package.

User and group administration

Accounts, groups, licences and mailboxes created, changed and removed as requested through your process.

Privileged access control

Administrative roles in the platform assigned with least privilege and, where your organization enables it, time-bound elevation.

Alert triage

Alerts from the platform that your organization routes to Moraph are reviewed and passed on with context to your security operations or CSSP.

Incident support

Moraph administrators support investigations and containment actions as directed by your security staff.

Access reviews

Periodic reviews of administrative and privileged access prepared for your ISSM to certify.

Licence management

Licence counts and assignments tracked against what your organization has purchased, with changes requested through your contracting office.

Service reporting

Regular reports on requests, changes, alerts, access reviews and Microsoft service notices, for your program office and security staff.

Integrations

How it connects to your systems

Connects toHowWhat flows
Your identity and credentialsUsers and Moraph administrators sign in with identities and credentials issued by your organization; Moraph does not issue or hold them.In: identities and group membership used for administration.
Your ticketing systemRequests, changes and incidents are worked in your organization's ticketing system where you require it, or in Moraph's service records on the classified network you approve.In and out: requests, change records and status.
Security operations or CSSPAlerts and incident information are passed to your security operations team or cybersecurity service provider as your procedures set.Out: triaged alerts with context. In: direction on response actions.
Change boardChange requests and security impact notes are prepared in the format your change board and ISSM use.Out: change requests and evidence. In: approvals and conditions.
Records managementRetention and records settings in the platform are configured to follow your records schedule as approved by your records officer.In: retention requirements.
Moraph Zero Trust overlayWhere your organization also uses Moraph's Zero Trust "Black Cloud" Overlay, administration of both is coordinated by the same service manager.Shared: change calendar and service reporting.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

Cleared US personnel

Every ticket for this service is handled only by Moraph staff who are US citizens with active clearances, verified by your security office.

Access under your authority

Moraph administrators use credentials and access your organization issues, from facilities and networks it approves, and lose access when you remove it.

Least privilege

Administrators hold only the platform roles their work needs, with time-bound elevation where your organization enables it.

Complete audit trail

Every Moraph action is tied to a request or change record and appears in the platform's audit log.

Encryption and keys

Moraph staff cannot use client encryption keys without explicit, time-bound authorization from your organization.

US-only operations

Service operations for US government clients take place only in the United States.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

10 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Service operations

Requests

For service owner and site IT leads

Requests received, completed and open, by type, site and age, against the targets agreed in the service description.

Break down by
Request type, Site or unit, Age, Status
Delivered as
Service review pack; export on request
Used for
Seeing where requests are waiting and where demand is growing.

Onboarding progress

For service owner and program office

Units and users brought on, in progress and planned, with open issues for each.

Break down by
Unit, Workload, Status
Delivered as
Service review pack
Used for
Tracking adoption against the plan your organization set.

Microsoft service notices

For service owner and ISSM

Service health incidents and announced changes from Microsoft, with Moraph's assessment of their effect on your environment.

Break down by
Notice type, Workload, Effect on baseline
Delivered as
Service review pack; notices sent as they arrive
Used for
Planning for platform changes and explaining service disruptions.

Licence position

For service owner and contracting office

Licences purchased, assigned and unassigned, by type.

Break down by
Licence type, Unit
Delivered as
Service review pack
Used for
Deciding on licence changes before renewal.

Security and access

Configuration baseline check

For iSSM and assessors

The results of Moraph's latest check of the tenant against the approved baseline, with any drift and its resolution.

Break down by
Workload, Setting area, Result
Delivered as
After each check; included in the service review pack
Used for
Evidencing that the environment matches its approved configuration.

Administrative access review

For iSSM

Every administrative and privileged role holder, Moraph and your own, with the role, when it was granted and the last review decision.

Break down by
Role, Organization, Review status
Delivered as
On the agreed review cycle
Used for
Certifying that administrative access is still needed and appropriate.

Alerts and incidents

For iSSM and security operations

Alerts routed to Moraph, how each was triaged and to whom it was passed, and incidents Moraph supported.

Break down by
Alert type, Outcome, Period
Delivered as
Service review pack; incident summaries as directed
Used for
Checking that alerts are handled under your procedures.

Governance

Change record

For iSSM, change board and assessors

Every change request with its purpose, security impact notes, approvals, implementation and verification.

Break down by
Change type, Approver, Status, Period
Delivered as
Service review pack; export for your authorization package
Used for
Evidencing that every change was approved before it was made.

Moraph staffing and clearance status

For service owner and security office

The Moraph staff assigned to your service, their role and the status of their clearance and qualification verification with your security office.

Break down by
Role, Verification status
Delivered as
Service review pack
Used for
Confirming that everyone working on the environment is cleared and qualified.

Service review actions

For service owner and Moraph service manager

Actions agreed at service reviews, their owner and their status.

Break down by
Owner, Status, Review date
Delivered as
Service review pack
Used for
Making sure what was agreed gets done.

Exports, access and evidence

  • Reports are prepared and held on the network your organization approves, and are classified and marked by your organization, not by Moraph.
  • The service review pack brings the service operations, security and governance reports together for each review with your program office.
  • Evidence for your authorization package, such as baseline checks and change records, is provided in the format your ISSM asks for.
  • Reports draw on both Moraph's service records and the platform's own logs, so the two can be compared.
  • Additional reports can be agreed with your service owner and added to the service description.

Deployment

Where and how it runs

Fully managed administration

Moraph's cleared staff carry out day-to-day administration of the tenant, with your organization approving changes and access.

Co-administration

Moraph administrators work alongside your own administration team, with responsibilities split as agreed in the service description.

Onboarding support only

Moraph supports configuration and onboarding, then hands day-to-day administration to your team.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Scope and baseline

We agree with your program office and ISSM which workloads, units and users are in scope, and document the configuration baseline your organization will approve.

Personnel verification

Moraph nominates administrators for your service, and your security office verifies their clearances, citizenship and qualifications before any access is granted.

Access and facilities

Your organization issues credentials and approves the facilities and networks from which Moraph staff will work.

Configuration

The tenant is configured against the approved baseline, and the evidence is recorded for your authorization package.

Procedures

Request handling, change, alert routing, incident support and access review procedures are agreed and written into the service description.

Onboarding and handover

Units and users are brought on in the order you choose, site IT leads are briefed, and the service moves into day-to-day operation.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • Moraph is not Microsoft. The platform, its features and its operation belong to Microsoft, and Microsoft's own service commitments, roadmap and outages apply.
  • Licences are bought and held under Microsoft's terms and your organization's contract vehicle; Moraph resells and manages them but does not set their terms.
  • Moraph does not hold or claim any authorization or accreditation for the platform or your environment. Authorization is maintained by Microsoft for the platform and by your authorizing official for your use.
  • Features available in Microsoft's Secret cloud can differ from commercial Microsoft 365, and Moraph cannot add features the platform does not provide.
  • Moraph staff work only under your organization's authority, with the access, credentials, facilities and networks it provides and approves.
  • Moraph does not provide classified network connectivity, end-user devices or facilities.
  • Moraph does not classify, mark or review content. Classification and handling decisions remain with your users and classification authorities.
  • Transfers of information between networks at different classification levels are not included in this service.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. Ask how Moraph's nominated administrators' clearances and qualifications will be verified by your security office
  2. Review a sample change request and security impact note in the format your ISSM uses
  3. Check the responsibilities table against your own authorization boundary
  4. Walk through how an alert would move from the platform to your security operations
  5. Review a sample access review and decide whether your ISSM could certify it
  6. Confirm which administration your team will keep and which Moraph will take on

Questions

Frequently asked questions

Does Moraph hold an authorization for this environment?

No. Moraph does not hold or claim any authorization or accreditation. Microsoft maintains the platform's authorization, and your authorizing official authorizes your use. Moraph prepares evidence of how the environment is configured and run to support your organization's process.

Who are the administrators?

Moraph staff who are US citizens with active clearances at the level your organization requires. Your security office verifies their clearances and qualifications before granting any access.

Can Moraph staff read our email and chat?

Administrators work with configuration, not content. They access content only when your organization directs it for a specific task, such as supporting an investigation, and every action is recorded.

What happens when Microsoft has an outage?

Microsoft's service commitments apply to the platform. Moraph tracks Microsoft's service notices, tells your service owner how the outage affects you, and works with Microsoft support on your behalf.

How is it priced?

Licences are priced under Microsoft's terms and your contract vehicle. Moraph's managed service is priced separately, usually by the number of users and the scope of administration. See Working with Moraph for what drives a quotation.

Can we keep some administration in-house?

Yes. Co-administration splits responsibilities between your team and Moraph as agreed in the service description.

Next steps

Evaluate DoD IL6 "Secret" Cloud Collaboration

Book a demonstration

See the product working with sample data, focused on your workflows.

Request a demonstration

Request a technical briefing

Architecture, integrations, security and hosting, with our engineers and your technical team.

Request a briefing

Factsheet

This page on two sides, to share with colleagues or add to your evaluation file.

Open the factsheet

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: DoD IL6 "Secret" Cloud Collaboration guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: DoD IL6 "Secret" Cloud Collaboration support guide.

Related products