HCW8045 - No TLS Certificate Name specified

Mohannad Ghabboun 20 Reputation points
2023-05-04T12:35:15.1266667+00:00

Hello There,

During HCW an error occurred indicating that the TLS certificate name was not specified. However, I checked the SAN of the certificate and both services SMTP and IIS are assigned, but still the issue persists.

Any idea of what might be the case here?

User's image

Microsoft 365
Microsoft 365
Formerly Office 365, is a line of subscription services offered by Microsoft which adds to and includes the Microsoft Office product line.
4,114 questions
Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
1,959 questions
{count} votes

Accepted answer
  1. Andy David - MVP 143.8K Reputation points MVP
    2023-05-04T17:06:10.5733333+00:00
    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
  1. Yuki Sun-MSFT 40,906 Reputation points
    2023-05-09T08:09:43.9333333+00:00

    Hi @Mohannad Ghabboun ,

    The error "No TLS certificate name specified" indicates it's likely to be an issue of the 3rd party TLS certificate. So, personally I'd recommend going through the linked document above once more to verify your certificate can meet the requirements in all details.

    Besides, it's suggested to confirm the FQDN you entered on the Organization FQDN page in HCW is correct.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Mohannad Ghabboun 20 Reputation points
    2023-09-11T05:59:44.9133333+00:00

    Hello Everyone,

    A quick update.

    The issue was related to a missing common name in the certificate and after using another certificate, the issue was resolved.

    0 comments No comments