Setting up and managing device configurations using Intune
The reliable way to confirm the cipher is to capture each device’s raw SCEP PKIOperation, decode its CMS/PKCS#7 payload, and read contentEncryptionAlgorithm from the inner EnvelopedData.
What determines the algorithm
Windows CertEnroll creates the SCEP request as an enveloped PKCS#7 message encrypted for the SCEP server’s encryption certificate. Its SCEP interface accepts server capabilities that set the preferred hash and encryption algorithms before creating the request.^1^ ^2^
However, Microsoft’s public documentation does not specify the complete selection order and fallback logic used by the Intune-managed Windows SCEP client. Therefore:
-
GetCACapscontributes capability preferences, but identical responses do not prove identical final algorithms. - The Intune profile’s Hash algorithm controls the request’s hashing family; it is not documented as a control for the PKCS#7 content-encryption cipher.^3^
- No documented Intune setting directly selects AES-128/192/256 for the SCEP envelope.
- The available documentation does not establish that FIPS policy, TLS cipher-suite policy, Group Policy, or Windows version alone determines this choice. Treat those as comparison variables, not confirmed causes.
The SCEP server certificates also matter: CertEnroll initialization expects CA, SCEP signing, and SCEP encryption certificates.^4^
Identify the cipher and OID
Obtain the complete PKIOperation request from the third-party service. This requires its cooperation or administrative access. A reverse proxy can capture it only where organizational policy permits TLS termination and inspection.
Depending on the SCEP implementation, the CMS value may be in the message query parameter or request body:
- Extract the value without truncation.
- URL-decode it.
- Base64-decode it.
- Save the resulting bytes as binary DER.
For example:
$encoded = Get-Content .\pkioperation-value.txt -Raw
$urlDecoded = [Uri]::UnescapeDataString($encoded.Trim())
# Preserve literal "+" characters when extracting from a raw query;
# some form decoders incorrectly convert them to spaces.
$der = [Convert]::FromBase64String($urlDecoded)
[IO.File]::WriteAllBytes("$PWD\request.p7b", $der)
certutil -asn .\request.p7b > .\request-asn1.txt
notepad .\request-asn1.txt
certutil -asn supports DER and PKCS#7 files.^5^
SCEP commonly has nested CMS structures. Do not identify the cipher from:
- the outer
SignedDatadigest algorithm; - the signer’s signature algorithm; or
- the recipient key-encryption algorithm, such as RSA.
Descend into the inner EnvelopedData, then locate:
encryptedContentInfo
contentEncryptionAlgorithm
algorithm: <OID>
Relevant AES-CBC OIDs are:^6^
| OID | Algorithm |
|---|---|
[IP Address].[IP Address].2 |
AES-128-CBC |
[IP Address].[IP Address].22 |
AES-192-CBC |
[IP Address].[IP Address].42 |
AES-256-CBC |
1.2.840.113549.3.7 |
3DES-CBC |
[IP Address].2.7 |
DES-CBC |
Finding [IP Address].[IP Address].22 at that exact location would prove the AES-192-CBC hypothesis.
Native tooling can also retrieve CMSG_ENVELOPE_ALGORITHM_PARAM, which returns the CRYPT_ALGORITHM_IDENTIFIER for an enveloped message.^7^
Compare affected and working devices
Run one controlled enrollment from each device and retain:
- Raw
GetCACapsandGetCACertresponses. - Exact
PKIOperationbytes. - Inner
contentEncryptionAlgorithmOID and parameters. - Outer digest/signature and recipient key-encryption OIDs, recorded separately.
- SCEP server encryption-certificate thumbprint and public-key type.
- Windows build, update level, effective cryptography policy, and Intune profile assignment.
On each device, correlate the attempt in:
Event Viewer → Applications and Services Logs → Microsoft → Windows → DeviceManagement-Enterprise-Diagnostic-Provider → Admin
Event 36 indicates that the SCEP request was generated successfully, but Microsoft does not document it as exposing the envelope cipher.^8^
If the DER payloads prove different ciphers while the server responses, certificates, profile, and policies are identical, submit both payloads and event exports through the Intune administration center support workflow or Microsoft Support for Business.
Windows 11 25H2 status
Microsoft’s public Windows 11 25H2 release-health page does not currently list a SCEP/PKCS#7 envelope-encryption issue for build 26200.9711.^9^ The build’s release notes likewise do not document a SCEP cipher-selection change.^10^
That does not exclude an undocumented regression; the captured inner OIDs are the necessary evidence before attributing the failure to 25H2.
References
- IX509SCEPEnrollment interface (certenroll.h)
- IX509SCEPEnrollment::CreateRequestMessage method (certenroll.h)
- ClientCertificateInstall CSP
- IX509SCEPEnrollment::Initialize method (certenroll.h)
- certutil
- Timing vulnerabilities with CBC-mode symmetric decryption using padding
- CryptMsgGetParam function (wincrypt.h)
- Troubleshooting device to NDES server communication for SCEP certificate profiles in Microsoft Intune
- Windows 11, version 25H2 known issues and notifications
- October 13, 2026—KB5127648 (OS Builds 26300.9711, 26200.9711 and 26100.9711) | Microsoft Support