LTI 1.3, Microsoft Entra ID SSO and REST API for AMTOS: Available on Request

Most EASA Part 147 MTOs don't run AMTOS in isolation. Many already use a general-purpose LMS for non-regulatory coursework, and most already run staff and student identity through Microsoft 365. Connecting AMTOS to either is something we set up for each school on request, as part of onboarding.

Three integrations are available on customer request: LTI 1.3 Advantage for embedding AMTOS inside an existing LMS, single sign-on with Microsoft Entra ID (Azure AD) or Google for identity, and a REST API for exchanging data with other systems. They are not switched on by default; tell us what you need and we include it in your onboarding plan.

LTI 1.3 Advantage — Embed AMTOS in Canvas, Moodle, or Blackboard

LTI (Learning Tools Interoperability) is the IMS/1EdTech standard that lets a specialised tool — like an exam engine — plug into a host LMS as if it were a native part of that platform. On request, AMTOS is connected through LTI 1.3 Advantage, the current version of the standard, which gives:

• Single launch point — a student clicks a link inside Canvas, Moodle, or Blackboard and is taken straight into the relevant AMTOS exam or course view, authenticated via OpenID Connect — no separate AMTOS login screen.
• Automatic grade pass-back — once a student completes an AMTOS exam, the result is posted back to the host LMS gradebook automatically via LTI Advantage Assignment and Grade Services (AGS). No manual re-entry of scores.
• Per-school configuration — each MTO configures its own LTI connection (issuer, client ID, deployment ID) against its own LMS tenant, so this works whether your organisation runs Canvas, Moodle, Blackboard, or another LTI 1.3-compliant platform.

In practice, this means AMTOS can sit behind the LMS your students already use daily for general coursework, while still handling the Part 66 question bank, exam engine, attendance, and CoR generation that a generic LMS was never built for.

Microsoft Entra ID SSO — One Identity, Not Two

Also on request, AMTOS can use single sign-on through Microsoft Entra ID (formerly Azure AD) or Google, using OpenID Connect. Staff and students who already have an organisational Microsoft account can log in to AMTOS with it directly — their sign-in is matched to their existing AMTOS Staff or Student record, and a local session is issued from there.

For MTOs that already standardise identity and access management through Microsoft 365, this removes a separate password to issue, reset, and secure — one less account for your IT team to manage, and one less login screen for your students and instructors to remember.

REST API: connect AMTOS to your other systems

For schools that run HR, ERP, rostering or Part-145 maintenance systems, a REST API can be provided on request. It lets those systems read and send the data they share with AMTOS, such as students and staff, enrolments, results and certificates, instead of exporting and importing spreadsheets. The scope is agreed with each school.

Who This Matters Most For

• MTOs already running a general LMS for non-regulatory coursework, who want a single entry point for students rather than two disconnected platforms.
• MTOs standardised on Microsoft 365 for staff and student identity, who want to fold AMTOS into their existing single sign-on setup instead of managing a separate credential.
• Quality and IT teams who want fewer manual grade-entry steps and fewer standalone accounts to secure and audit.

If your organisation doesn't use an external LMS or Microsoft 365 identity today, nothing changes — AMTOS continues to work exactly as a complete, standalone Part 147 platform. LTI, single sign-on and the REST API are integration options available on request, not a requirement.