I looked at your support case but it looks like you closed it and used (because of urgency) a workaround. Can you tell us what exactly you did?
From what I know about a 409 conflict error in Azure IaaS: It means you are trying to create the VM but there is still a reference in Azure (somewhere) that causes a conflict. Could be the same UID / naming somewhere or whatever else. When you (for example, not saying this is / was the problem) have a VM in Azure, delete it, and immediately start the restore from B&R you can be "too fast". The delete operation in Azure can take longer than what you can see in the UI. But again, this is just an example, it could be completely different