We have encountered a critical error today - we are no longer able to create bacpac files of our live Azure production databases. Everything was working up until now, and su
well I fell your pain... the answer here is: Replace your schema...There's no other way...
Instead of 'Column Name'
use [Column Name]
... instead of Select CryptColumnA 'Column A' from myTable
use Select CryptColumnA as [Column A] from myTable
and so forth...
We have filed a support ticket with Microsoft and the issue was acknowledged as a bug. We only had a problem with bacpac export, not import - and apparently it was due to a SQL Azure change which hardened some of the export validations.
To make the long story short, the issue has been fixed by Microsoft and we are no longer experiencing the problem - and that is without any schema changes on our end.