It's a known problem – there's a cyclic dependency in the Azure API itself so this isn't possible in a single run without some kind of hacks.
Cert creation depends on custom domain to be deployed and to update the SSL binding on the custom domain it needs to know the cert thumbprint.