"Service '<your service name>' has zero application (non-infrastructure) endpoints. This might be because no configuration file was found for your application, or because no service element matching the service name could be found in the configuration file, or because no endpoints were defined in the service element."}

 

This error message looks so vague which sometimes you only have to make sure that your service name (or service namespace if you're using AppFabric Service Bus) is correctly spelled. 

HTH!

When accessing my deployed WCF in local website (running IIS 7, Windows Server 2008) I got the "Error 503 Service is unavailable". This happens because DefaultAppPool is set to Stopped. So, to resolve the issue - I just started the application pool.

 

But after which, I just created a new Application Pool dedicated for my WCF REST Service. 

After several weeks working in Azure, we were able to run Java, Python, MySql in Windows Azure. That's cool!