Skip to main content

Double Key Encryption (DKE)

Applies to:
Microsoft 365 E5Microsoft PurviewAzure RMSDuoKey MPC

Product teaser

Double Key Encryption for Microsoft 365

The product teaser shown on duokey.com.

Introduction & Concepts​

Modern work environments, especially those using cloud services, require advanced data protection. While standard permissions and encryption offer baseline security, Microsoft Purview Information Protection (MPIP) strengthens it by encrypting data and embedding usage rights directly with the information.

Important

For highly sensitive data, even stronger safeguards are needed—particularly protection from the cloud provider itself. This is where Double Key Encryption (DKE) comes in.

The Challenge: Protecting Sensitive Data in the Cloud​

Key Control

Cloud providers typically manage the encryption keys

Technical Access

Providers have technical ability to access encrypted data

Shared Control

Shared control poses regulatory and compliance challenges

Microsoft Purview Information Protection (MPIP)​

Before exploring DKE, it's essential to understand MPIP/Azure RMS, which DKE extends.

ComponentDescription
Microsoft Entra IDManages identities and tenant separation
Purview Information ProtectionHandles sensitivity labels and protection settings
Azure Rights Management (Azure RMS)Manages Microsoft-controlled cryptographic keys
ClientsApps (e.g., Microsoft 365) accessing protected content
DKE Web ServiceCustomer-controlled component for DKE flow

What is Double Key Encryption?​

Double Key Encryption (DKE) builds directly on top of Microsoft Purview Information Protection. It achieves maximum data confidentiality and control by introducing a second encryption key.

Two Keys

One key managed by Microsoft, second key held exclusively by you

Customer Control

Microsoft has no access to your private, second key

Data Privacy by Design

DuoKey can never access your document content

Swiss Cloud Service

HSM-protected keys with DuoKey MPC

DuoKey - DKE​

DuoKey DKE is a Swiss cloud service offering Double Key Encryption to encrypt Microsoft 365 Office documents with Hardware Security Module protected keys.

Architecture

DuoKey DKE with Microsoft 365

DuoKey DKE with Microsoft 365The Office client signs in with Entra ID, gets key 1 from Azure RMS and key 2 from the DuoKey DKE web service, which checks your Zero Trust policy and decrypts with the MPC vault.MICROSOFT 365DUOKEY · SWISS CLOUDSIGN INKEY 1KEY 2 · HTTPSENFORCEDECRYPTCONFIGURECLIENTOffice clientWord · Excel · PPTIDPMicrosoft Entra IDidentityKEY 1Azure RMSkey 1 · MicrosoftPOLICYZero Trust policyuser · geo · device · groupsKEY 2DKE web servicekey 2 · you controlVAULTMPC vaultshares · CH · EU · your DCYOUYour adminaccess rulesLEGENDDuoKey key serviceMicrosoft / your orgClientKey 2 requestCall

Key 1 stays with Microsoft in Azure RMS. Key 2 is served by the DuoKey DKE web service, which checks your Zero Trust policy before every decrypt and computes with key shares held across the MPC vault.

The DuoKey DKE Solution Provides​

  • The customer-controlled private key (DKE Key Management)
  • The deployment of DKE Web Service apps
  • Control of DKE service access

How Double Key Encryption Works​

Exploded view

Anatomy of a DKE-protected document

Anatomy of a DKE-protected documentExploded view of a Double Key Encrypted document: the content, the access metadata encrypted first with your DuoKey key, and the outer layer encrypted with the Microsoft key.Document contentENCRYPTED · CONTENT KEYDKE layerKEY 2 · DUOKEY · APPLIED 1STAzure RMS layerKEY 1 · MICROSOFT · 2ND

The access metadata that unlocks the content is encrypted twice: first with your DuoKey key, then with the Microsoft key. Opening the document needs both. Source: Microsoft Learn, DKE encryption workflow.

Sequence

Protecting a document with DKE

Protecting a document with DKEThe Office client signs in with Entra ID, collects the Azure RMS public key and the DuoKey DKE public key, then encrypts the access metadata first with the DKE key and then with the Azure key.1 SIGN INTOKEN1 BOOTSTRAP2 AZURE PUBKEY3 GET PUBKEY4 DKE PUBKEY5 DKE LAYER6 AZURE LAYERCLIENTOffice clientWord · Excel · OutlookIDPMicrosoft Entra IDuser authorizationMICROSOFTAzure RMSkey 1 · MicrosoftDUOKEYDuoKey DKE servicekey 2 · you controlLEGENDCallReturnYour keyLocal step on the clientMicrosoftDuoKey

Steps 1 to 6 of Microsoft's DKE encryption workflow. The client caches the Azure public key (30 days by default) and the DKE public key, so later documents are protected without calling either service. Source: Microsoft Learn, DKE encryption workflow.

Critical Security Considerations​

Warning

DKE provides powerful control, but its security effectiveness is entirely dependent on your organization's ability to secure its components.

ConsiderationDescription
Protect Your KeyThe primary security requirement is rigorously safeguarding the customer-controlled private key
Protect IdentitiesProtecting user and administrator identities authorized to access the DKE service is critical
Identity Provider RiskUsing the same identity provider for both M365 and DKE introduces risk of single identity compromise

DKE Components​

ComponentDescription
Client FunctionalityMicrosoft 365 desktop apps on Windows (Word, Excel, PowerPoint, Outlook) and Adobe Acrobat
DKE Web ServiceWeb server component operated by DuoKey and controlled by the customer

Comparison: Standard MPIP vs. DKE​

FeatureStandard MPIPDKE (with DuoKey)
Who holds encryption key?Microsoft (cloud provider)Microsoft + Customer (DuoKey HSM)
Can Microsoft access content?Technically possible (with limitations)No access possible
Control over sensitive dataShared controlExclusive customer control
Compliance with regulationsLimited (depends on jurisdiction)Enhanced compliance

What's Next​

Vendor Documentation​

Tip

Book a 30-Minute Demo: Schedule a personalized demo to explore how DKE can benefit your organization.