Artifact GuideEU

DMA Interoperability Articles 6(7) and 7

Use this page to separate the DMA's two main interoperability tracks: Article 6(7) access to gatekeeper hardware and software features, and Article 7 interoperability for number-independent interpersonal communications services.

Grounded in the DMA text, Commission interoperability Q&A, resources for businesses, and Commission compliance-report expectations for technical, security, privacy, and evidence records.

Author
Sorena AI
Published
May 9, 2026
Updated
May 25, 2026
Sections
5

Structured answer sets in this page tree.

Primary sources
4

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated May 25, 2026
Overview

DMA interoperability is not one generic access duty. Article 6(7) requires a designated gatekeeper to provide free and effective interoperability with certain hardware, software, operating-system, and virtual-assistant features made available to the gatekeeper's own services or hardware. Article 7 separately governs number-independent interpersonal communications services and includes reference offers, reasonable interoperability requests, security preservation, and strict limits on personal-data exchange.

Section 1

Separate Article 6(7) feature access from Article 7 messaging interoperability

Article 6(7) is the product and platform-feature obligation. It applies where the designated core platform service includes an operating system or virtual assistant and the gatekeeper's own services or hardware access or control hardware or software features that third-party service or hardware providers need for interoperability.

Article 7 is narrower but more process-heavy. It applies where a designated gatekeeper provides a number-independent interpersonal communications service, and another provider offering or intending to offer such a service in the Union requests interoperability for the listed basic functionalities.

  • Use Article 6(7) for operating-system, virtual-assistant, hardware, and software feature access needed by service providers, hardware providers, business users, or alternative providers.
  • Use Article 7 for messaging-service interoperability: one-to-one text, file sharing, group messaging, voice calls, and video calls as the staged basic functionalities become applicable.
  • Do not treat a developer API, device pairing feature, data portability request, advertising measurement request, and messaging interoperability request as the same queue.
  • Record the designated gatekeeper, designated core platform service, requested feature or functionality, requesting party, free-of-charge access point, and security or integrity condition.
Section 2

Article 6(7): what a request should identify

An Article 6(7) request should be anchored to a concrete feature, not to a broad desire for platform access. The DMA compares third-party access with the same hardware and software features that are accessed or controlled through the gatekeeper's listed operating system or virtual assistant and are available to the gatekeeper's own services or hardware.

For connected-device and app integrations, the useful evidence is technical: the feature requested, the gatekeeper-controlled interface or operating-system functionality, the third-party use case, the equivalent gatekeeper use, the proposed interoperability route, and any stated integrity, security, or privacy limitation.

  • Name the feature or capability: for example notifications, pairing, local connectivity, file transfer, media casting, NFC reader/writer use, background execution, or automatic audio/Wi-Fi behavior when those are grounded in the Commission's Apple materials.
  • Identify whether the requester is a provider of services, provider of hardware, business user, or alternative provider of services supplied with or in support of a core platform service.
  • Check whether the gatekeeper has made guidance, API documentation, request forms, trackers, or contact points available for the relevant operating system.
  • Keep the gatekeeper's reason for any refusal, delay, or security condition alongside the technical test evidence, because Article 6(7) permits only strictly necessary and proportionate integrity measures that are duly justified.
Section 3

Article 7: reference offers, reasonable requests, and user choice

Article 7 requires a gatekeeper that provides a listed number-independent interpersonal communications service to make basic functionalities interoperable by providing technical interfaces or similar solutions, upon request and free of charge.

The gatekeeper must publish a reference offer with technical details, general terms and conditions, and necessary details on security and end-to-end encryption. After that publication, another provider offering or intending to offer such services in the Union may request some or all listed basic functionalities, and the gatekeeper must comply with a reasonable request within three months by making the requested basic functionalities operational.

  • Check whether the requester is a provider of number-independent interpersonal communications services in the Union or intending to offer them in the Union.
  • Map the requested functionality to the Article 7 list: one-to-one text and file sharing, group messaging and group file sharing, and later voice or video call functionality where applicable.
  • Store the published reference offer version, technical interface details, general terms, security and encryption statements, request date, reasonableness assessment, and operational readiness evidence.
  • Do not force end users into interoperability: Article 7 preserves the freedom of users of both services to decide whether to use interoperable basic functionalities.
Section 4

Security, integrity, privacy, and product-review evidence

Both interoperability tracks allow security-related controls, but neither permits unsupported product discretion. Article 6(7) allows strictly necessary and proportionate measures to protect the integrity of the gatekeeper's operating system, virtual assistant, hardware, or software features, if duly justified. Article 7 similarly allows strictly necessary and proportionate measures to protect integrity, security, and privacy of messaging services.

A grounded review file should therefore show the requested access, the risk being controlled, the less-restrictive alternatives considered, the technical test results, and why the selected condition does not defeat effective interoperability.

  • Keep architecture notes, API or interface documentation, test results, compatibility findings, abuse-case analysis, and release notes for each interoperability measure.
  • For Article 7, preserve evidence that the gatekeeper's own security level, including end-to-end encryption where applicable, is preserved across interoperable services.
  • For personal data exchanged under Article 7, document why each data element is strictly necessary for effective interoperability and how GDPR and ePrivacy compliance is handled.
  • When a gatekeeper rejects, delays, narrows, or conditions access, keep the written reason, technical basis, proportionality analysis, reviewer identity, and any appeal, independent review, conciliation, or Commission-facing record.
Section 5

How to review an interoperability implementation before relying on it

A useful Article 6(7) or Article 7 review does not end when a request form is submitted. The implementation record should prove that the correct DMA track was chosen, the request was handled through the right public or gatekeeper process, and the resulting access works in practice without extra friction that undermines equivalence.

For gatekeepers, the same record feeds Article 11 compliance reporting. For business users and third-party providers, it supports escalation, follow-up questions, and product planning when the gatekeeper's process, documentation, tracker, or decision is incomplete.

Does DMA Article 6(7) require every operating-system feature to be opened to every developer?

No. Article 6(7) is tied to features accessed or controlled through the designated operating system or virtual assistant and available to, or used by, the gatekeeper's own services or hardware. The request still needs a concrete interoperability purpose, and the gatekeeper may justify strictly necessary and proportionate integrity measures.

What is the key Article 7 evidence for a messaging interoperability request?

Keep the gatekeeper's reference offer, the requested basic functionalities, the request date, the reasonableness assessment, technical-interface evidence, the three-month operationalisation record, security and encryption analysis, user-choice handling, and the strict-necessity basis for any personal data exchange.

  • Classify the request as Article 6(7), Article 7, or outside these provisions before starting technical work.
  • Attach the public reference offer, resource page, request form, technical reference, tracker entry, or gatekeeper response that controls the workflow.
  • Compare the third-party experience with the gatekeeper's own service or hardware where Article 6(7) equivalence is the issue.
  • For Article 7, verify request reasonableness, three-month operationalisation evidence, security preservation, end-user choice, and strict data minimisation.
  • Record open issues separately: missing documentation, unavailable interfaces, unclear eligibility criteria, rejected requests, non-public confidentiality constraints, or security claims that lack a technical explanation.
Recommended next step

Use this guide to classify and evidence Article 6(7) and Article 7 work

Sorena can help map DMA interoperability requests to the correct obligation, cited source, product owner, technical evidence, security review, and follow-up record.

Primary sources

References and citations

digital-markets-act.ec.europa.eu
Referenced sections
  • Commission practical-information page hosts DMA submission materials; the Article 11 template expects technical, engineering, security, API, OS-functionality, indicator, and justification evidence for Articles 5 to 7 compliance.
"Compliance Report Template Form"
digital-markets-act.ec.europa.eu
Referenced sections
  • Commission page points businesses to gatekeeper resources for operating-system interoperability requests, documentation, and request-status information.
"resources for businesses"
eur-lex.europa.eu
Referenced sections
  • DMA text supplies the controlling Article 6(7) and Article 7 conditions for classification, requests, and implementation review.
"upon request, and free of charge"
Related guides

Explore more topics

DMA Anti-Circumvention Design Review for Gatekeeper Product Changes
Review DMA Article 13 anti-circumvention risks in gatekeeper product, interface, contractual, commercial, and technical changes with obligation mapping and evidence records.
DMA Article 11 Compliance Report Template FAQ
How gatekeepers should use the DMA Article 11 compliance report template to document obligation-by-obligation measures, evidence, updates, and non-confidential summaries.
DMA Article 6 Business User Data Access Guide
Grounded guide to EU Digital Markets Act Article 6 data access for business users, end users, authorised third parties, consent boundaries, and evidence handoffs.
DMA Articles 5, 6 and 7 obligations mapped to CPS evidence
Map EU Digital Markets Act Articles 5, 6 and 7 obligations to affected core platform services, product evidence, legal owners, and Article 11 compliance-report artifacts.
DMA compliance program and monitoring for gatekeepers
Build a DMA compliance program around Article 8 effective compliance, Article 11 reporting evidence, Article 13 anti-circumvention controls, and Article 28 compliance-function governance.
DMA Core Platform Service Scoping
Scope EU Digital Markets Act core platform services by service category, designation evidence, user thresholds, and Form GD service-boundary records.
DMA core platform services FAQ
FAQ on EU Digital Markets Act core platform services: Article 2 service categories, gatekeeper designation evidence, user thresholds, service scoping, and Article 11 reporting.
DMA CPS Obligation Matrix Workflow: Articles 5, 6, 7 and Article 11 Evidence
Build a DMA core platform service obligation matrix that links each designated CPS to Articles 5, 6 and 7 duties, product owners, designation evidence, Article 11 report artifacts and review gates.
DMA designation intake workflow for gatekeeper notifications
Build a grounded DMA designation intake record covering core platform service classification, Article 3 thresholds, Form GD evidence, Commission handoff, and Article 11 readiness.
DMA enforcement, penalties, and remedies: Commission powers and evidence
EU Digital Markets Act enforcement guide covering Commission non-compliance decisions, DMA fine caps, periodic penalty payments, remedies, interim measures, commitments, and Article 11 evidence.
DMA Gatekeeper Compliance Checklist for Articles 5, 6, 7 and 11
A grounded EU Digital Markets Act checklist for designated gatekeepers: core platform service scope, Article 5/6/7 controls, Article 11 report evidence, anti-circumvention checks, and review gates.
DMA Gatekeeper Designation Guide: Article 3 thresholds, Form GD, and Article 11 readiness
A grounded EU Digital Markets Act guide for assessing Article 3 gatekeeper thresholds, scoping core platform services, preparing Form GD evidence, handling rebuttal annexes, and planning Article 11 compliance reporting.
DMA gatekeeper thresholds: what counts and when to notify
Standalone FAQ on the EU Digital Markets Act gatekeeper thresholds, Article 3 notification timing, Form GD evidence, and active user-count methodology.
DMA interoperability requests: Article 7 and Commission guidance
How EU Digital Markets Act interoperability requests work for Article 7 messaging services, Article 6(7) operating-system access, gatekeeper evidence, requester evidence, and security safeguards.
DMA penalties and fines: caps, triggers, and enforcement evidence
EU Digital Markets Act penalties guide covering Article 30 fine caps, Article 31 periodic penalty payments, non-compliance decisions, remedies, and evidence records.
DMA Product Change Review Workflow for Articles 5, 6, 7, 11 and 13
Review DMA-relevant product releases for Article 5, Article 6, Article 7, anti-circumvention, Article 11 evidence, and product-owner/legal signoff.
DMA Self-Preferencing Compliance Examples for Ranking and Display
Examples and release-review controls for DMA Article 6(5) self-preferencing checks across ranking, indexing, crawling, search results, marketplaces, app stores, feeds, and virtual assistants.
DMA vs Data Act: gatekeeper duties compared with EU data-sharing rules
Compare the EU Digital Markets Act and EU Data Act by scope, actors, data access, interoperability, reporting, evidence, and enforcement without merging distinct obligations.
DMA vs DSA: Digital Markets vs Services Act
A grounded comparison of the DMA and DSA focused on gatekeepers, core platform services, DMA obligations, Article 11 reporting, interoperability, data access, and enforcement.
DMA vs EU competition law: gatekeeper obligations, Article 11 evidence, and enforcement
Compare the EU Digital Markets Act with EU competition law: ex ante gatekeeper and core platform service duties, Articles 5 to 7, Article 11 reports, penalties, and evidence records.
DMA vs GDPR: gatekeeper data obligations compared
Compare DMA gatekeeper obligations with high-level GDPR overlap for consent, combining personal data, data access, portability, and Article 11 reporting.
EU Digital Markets Act Article 11 Evidence Calendar
Build a source-grounded DMA Article 11 compliance report calendar with evidence owners, annual update checkpoints, report sections, and review gates.
EU Digital Markets Act checklist for gatekeeper compliance
A source-grounded DMA checklist for designated gatekeepers and core platform services, covering scope, Articles 5, 6 and 7 obligations, Article 11 reporting, evidence, anti-circumvention, and governance.
EU Digital Markets Act compliance: gatekeeper obligations and evidence
DMA compliance guide for designated gatekeepers: core platform service scoping, Articles 5, 6 and 7 controls, Article 11 reports, anti-circumvention checks, interoperability evidence, and enforcement risk.
EU Digital Markets Act deadlines and compliance calendar
Track DMA notification, designation, six-month obligation start, Article 11 reporting, Article 14 concentration notices, Article 15 profiling audits, and preparation milestones using official EU sources.
EU Digital Markets Act FAQ: gatekeepers, DMA obligations, reports, and enforcement
Concise FAQ on the EU Digital Markets Act for gatekeeper designation, core platform services, Articles 5, 6 and 7 obligations, Article 11 reports, interoperability, business-user data access, compliance evidence, and enforcement.
EU Digital Markets Act requirements for gatekeepers
DMA requirements for designated gatekeepers: core platform service scope, Articles 5, 6 and 7 obligations, Article 11 reporting, anti-circumvention, evidence, remedies, and fines.
EU Digital Markets Act Timeline and Key Milestones: practical obligations and evidence guide
Practical EU Digital Markets Act guide to Timeline and Key Milestones: scope, owners, evidence, edge cases, checklist steps, and external source-linked citations.
EU DMA Applicability Test: gatekeeper thresholds, core platform services, and evidence
Test whether the EU Digital Markets Act may apply to a platform service using the DMA gatekeeper criteria, core platform service categories, EU user thresholds, notification steps, and evidence records.
EU DMA Article 11 Compliance Reporting Guide
Source-grounded guide to EU Digital Markets Act Article 11 compliance reports: report purpose, template evidence, non-confidential summaries, annual updates, and submission steps.
EU DMA do's and don'ts for product teams
Product release checks for designated DMA gatekeepers: Article 5, 6 and 7 obligations, anti-circumvention review, data access, interoperability, self-preferencing and Article 11 evidence.
What do DMA Articles 5, 6, and 7 require from gatekeepers?
FAQ explaining how EU Digital Markets Act Articles 5, 6, and 7 group gatekeeper obligations, what product evidence they require, and how Article 11 reporting connects.