Skip to content
PolicyAction required

DAI system access requests now route through DISA E-ICAM, not ARMS

MARADMIN 453/26·September 29, 2026·4 min read·Official source

The Marine Corps cut over Defense Agencies Initiative (DAI) user access provisioning from the legacy Access Request Management Service (ARMS) to the DISA Enterprise Identity, Credential, and Access Management (E-ICAM) system on 16 September 2026. ARMS is now read-only. All new access requests, role modifications, and account recertifications go through DISA E-ICAM going forward.

Heads up: If you submitted a SAAR in ARMS between 29 August and 15 September 2026 and it was not fully provisioned, you must resubmit it through DISA E-ICAM.

Who it affects

This touches anyone in the Marine Corps Total Force who has or manages DAI access, specifically:

  • Active DAI users (anyone with a DAI account)
  • Information Owners (IOs) in G-1, G-4, or G-8 shops
  • Supervisors who approve DAI access requests
  • Security managers who review SAARs
  • Comptrollers, supply, logistics, and finance personnel

If you have never touched DAI, this does not apply to you.

What you need to do

The action depends on your role.

All DAI users:

  1. Stop using ARMS for new requests. Go to DISA E-ICAM instead. The link is on the SDI SharePoint: https://usmc.sharepoint-mil.us/sites/dcpr/sitepages/sdi.aspx
  2. If your SAAR was submitted in ARMS between 29 August and 15 September 2026 and was not fully provisioned by 28 August, resubmit it through DISA E-ICAM. Watch for the formal task list from HQMC SDI.
  3. Upload a current cyber awareness certificate with each SAAR. This is required until DISA connects to learning management systems automatically.
  4. If you are a first-time DAI user, complete DAI self-registration before requesting access. Instructions are in the DAI smart pack at the link above.
  5. Monitor your own requests in DISA E-ICAM through final approval. Do not assume it went through.

SAAR submission rules (read before submitting):

  • Do not mix Oracle Time and Labor (OTL) roles with full financials roles on the same SAAR.
  • Do not mix Supply Chain Management (SCM) and Financial Management (FM) roles on the same SAAR.
  • Only combine roles on one SAAR if they follow the same approval workflow. Roles that require a DD Form 577 and roles that do not must go on separate SAARs.
  • If your role covers multiple UICs or DoDAACs, request the role once using your own organization's UIC. You do not need duplicate requests.

Supervisors:

  • Log into DISA E-ICAM before your users submit, or they cannot select you as their supervisor.
  • When reviewing a SAAR: validate the user's info, confirm the access fits their duties, check all required documentation, fill in every field marked with a red asterisk (cyber awareness date, contractor period of performance if applicable), and select a security manager for your organization.

Information Owners:

  • Your current ARMS IO appointment letter is valid through 30 November 2026.
  • Submit your DISA E-ICAM IO appointment letter and training certificate by 30 November 2026. This will come as an ETMS2 tasker.
  • Review and act on provisioning requests within 21 days of submission.
  • For users restoring a previously held (end-dated) role: they submit a DISA E-ICAM SAAR, then contact you to remove the end date in DAI.
  • Coordinate with supervisors to revoke access immediately when someone PCS's, separates, or no longer needs a role.

Security managers:

  • When reviewing a SAAR, check DISS and annotate the user's security clearance level and active status in the SAAR before routing.

Key dates

DateEvent
28 August 2026Cutoff for ARMS bulk migration to E-ICAM
29 Aug – 15 Sep 2026SAARs submitted in ARMS during this window must be resubmitted in E-ICAM
16 September 2026E-ICAM go-live. ARMS no longer used for new requests
November 2026DAI role auto-provisioning expected (manual provisioning by HQMC SDI UMX until then)
30 November 2026IOs must submit DISA E-ICAM appointment letter and training certificate
30 September 2027ARMS fully decommissioned

All existing migrated SAARs show a system-generated effective date of 15 July 2026. That date controls when recertification is triggered in E-ICAM unless something else, like a supervisor change, happens first.

The official version

Full guidance is in MARADMIN 453/26. This message also references MARADMIN 091/25 (DAI Information Owner guidance) and MARADMIN 136/25 (DAI user access procedures).

Training materials, SOPs, and support channel links are on the HQMC SDI SharePoint: https://usmc.sharepoint-mil.us/sites/dcpr/sitepages/sdi.aspx

For questions, start with your local IO. HQMC SDI UMX is running an open support channel through November 2026 (link on the SharePoint above). HQMC POCs are listed in the MARADMIN.

This is written by a reservist, for reservists. It is not an official publication of HQMC or MARFORRES. Always verify guidance with your command or unit S-1 before acting on any article or summary.

Resources & references

The documents this bulletin points to, with a plain-English note on why each matters. Links marked CAC required need a government login.

  • DON Policy Memorandum on Modernizing SAAR and Account Provisioning through ICAM Workflows (Ref A)Reference

    This Department of the Navy memo establishes policy for modernizing System Access Authorization Requests and account provisioning through ICAM workflows. It is one of the two authority documents driving the DAI-to-E-ICAM transition described in this MARADMIN.

  • DoW Memorandum on Accelerating Adoption of ICAM (Ref B)Reference

    This Department of War memorandum directs accelerated adoption of Identity, Credential, and Access Management across the enterprise. Along with Ref A, it is the policy basis requiring Marines to move DAI access requests into DISA E-ICAM.

  • DAI Information Owner Appointment Guidance (MARADMIN 091/25)MARADMIN

    This earlier MARADMIN covers how DAI Information Owners are appointed and validated. Reservists who are IOs or who need to work with IOs for access restoration should be familiar with it.

  • DAI User Access Procedures (MARADMIN 136/25)MARADMIN

    This earlier MARADMIN established DAI user access procedures. It provides the procedural baseline that the current MARADMIN is updating with the new DISA E-ICAM workflow.

policyaccountabilityleadership

Take it to drill

A one-page brief you can print or save. Built for SNCOs to brief their Marines.