30 Mar’17

Dynamics 365, EnterpriseInvalid Namespace Error


We have an integration of CRM with 3 party system which sends sales data. We used Azure service bus to send data from CRM to 3 party system in real time. It was working fine until CRM 2016 But after upgradation of dynamics CRM to Dynamics 365 our integration stopped.


We decided to check why our integration has stopped so, we checked the system log and we found there is some issue with service connection.

After diagnosis of error we try to update the Azure service bus but we were not able to update the service end point. We continuously receiving the same error “Invalid Namespace” So we tried another approach and decided to create new service end point.

I have followed the below steps for registration.

  • Register a new Service Endpoint
  • Add the connection string from Service Bus portal.
  • Select the Designation Type as “Two way”
  • Error occurs “Provide a valid Namespace Address” while saving it.


We connected with Microsoft and they suggested that there is slight modification in the Namespace Address. To resolve this issue you need to change Namespace Address from sb:// to https://

sb://xxx.servicebus.windows.net/abc/xyz -> https://xxx.servicebus.windows.net/abc/xyz


Sometime unknown minor issues will stop your whole integration process and it will be not known to you.

Hope this blog help you resolve your service bus integration issue.


Written by

Subhash Mahato

Technical Consultant

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload the CAPTCHA.

Want to streamline your business processes?

  • This field is for validation purposes and should be left unchanged.

Recent Articles

  • Dynamics 365 Client Diagnostics

    15 March’ 2018

    Main cause of Performance Issues: Bandwidth and latency are the primary characteristics which affects the performance o...

    Read more
  • Closing Blind Shift in MPOS and CPOS in Dynamics 365 for Retail

    15 March’ 2018

    Manual For closing Blind shift in POS: Blind shifts terminate the currently ongoing shift and when logged in a new shif...

    Read more
  • Persistent Filters in the Power BI Service

    13 March’ 2018

    Introduction: The feature is finally release, and it is power BI has announced general availability of persistent filt...

    Read more
  • Cause and Solution for Scribe MSMQ not receiving Message from AX

    10 March’ 2018

    Issue: Microsoft Message Queuing (MSMQ) service running on Server might be unable to receive messages. Therefore, messa...

    Read more
  • User Privileges on SharePoint – D365 Document Integration

    10 March’ 2018

    Overview: Often, we wonder what could be wrong where we see a generic error on Documents in Dynamics 365. Something lik...

    Read more