Others

Sync userSMIMECertificate to Microsoft 365 with Azure AD Connect

Jason MillerJason Miller Nov 18, 2026 869 views

Question details

Learn how to populate the userSMIMECertificate attribute in Active Directory and troubleshoot its synchronization to Microsoft 365.

Sync userSMIMECertificate to Microsoft 365 with Azure AD Connect
Product
Microsoft 365, Outlook, and Microsoft Entra Connect Sync (formerly Azure AD Connect)
Device & OS
not provided
Scenario
S/MIME certificates have been deployed in Active Directory, and the administrator wants users' certificate information available in Microsoft 365.
Observed behavior
Published certificates are visible in Active Directory, but userSMIMECertificate is empty for users.
Before you start

Confirm that the user has an S/MIME certificate in the Personal certificate store and can access classic Outlook. To troubleshoot synchronization, obtain access to the Microsoft Entra Connect Sync server and its synchronization tools.

Solution 1Recommended

Publish the S/MIME certificate to the Global Address List

Use Outlook to populate userSMIMECertificate when the attribute is empty in Active Directory.

Outlook publishes certificates from the user's Personal certificate store in PKCS #7 format. The userCertificate and userSMIMECertificate attributes are distinct; do not copy the same certificate value directly between them.

1
Check the certificate

On the user's computer, open the Personal certificate store and verify that the user's S/MIME certificate is present.

2
Open email security settings

In classic Outlook, select File > Options > Trust Center > Trust Center Settings > Email Security.

3
Publish the certificate

Select Publish to GAL to publish the user's certificate to the Global Address List.

4
Verify the attribute

In Active Directory Users and Computers, enable View > Advanced Features, open the user's Properties, and check userSMIMECertificate on the Attribute Editor tab.

Publish the S/MIME certificate to the Global Address List
Published certificates are not necessarily the same attribute: A certificate visible under Published Certificates or in userCertificate does not by itself mean that userSMIMECertificate is populated.
Free Microsoft Office alternative

Work with Office documents in WPS Office

WPS Office is a free, lightweight alternative for working with Office documents. Its familiar interface and Microsoft Office format compatibility make it easy to move existing files, but it does not configure or repair Microsoft 365 S/MIME certificate synchronization.

A familiar interface for working with Office documentsCompatible with Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXA lightweight option for editing and sharing documents alongside your Microsoft 365 workflowFree tools for opening and editing common office files
microsoft office alternative - wps office

Frequently Asked Questions

Why is userSMIMECertificate empty when a certificate is already published in Active Directory?

The certificate may be stored in a different attribute, such as userCertificate. In classic Outlook, use File > Options > Trust Center > Trust Center Settings > Email Security > Publish to GAL to publish the user's S/MIME certificate.

Can I copy userCertificate directly into userSMIMECertificate?

No. The attributes are distinct, and Outlook publishes the S/MIME certificate information in PKCS #7 format. Use Outlook's Publish to GAL action rather than copying the same certificate value directly.

Where can I check whether the attribute reached the sync engine?

On the Microsoft Entra Connect Sync server, open Synchronization Service Manager. Search the Active Directory connector space for the user, then use Metaverse Search to inspect the corresponding object and its attributes.

What should I check if the attribute is present on-premises but unavailable in Microsoft 365?

Inspect the user in the connector spaces and metaverse, review the applicable synchronization rules, and check the Operations tab for errors. Then verify the result after the next synchronization cycle.