That table has existed for a long time and as far as I know has never had a problem in SqlAzure.
However, when I look at it in sql management tools using design view and then click the manage indexes and keys button in the upper left toolbar, I see that when I click on the primary key for "Create as Clustered" it says no, so I guess the thing to try is changing that to yes. I see it is yes on other tables. So on your local machine in sql management tools right click the table and choose design, then click the toolbar icon in the upper left for manage indexes and keys, then click on the index named PK_ws_Discount then change create as clustered to yes if it possible, save it and try again with the migration.
I've never had any trouble with running our sql setup scripts on a new sql azure database so not sure why it is having a problem on migration.
Hope that helps,