Edited Issue: Designer: All primary keys should be clustered (affects SQL Azure) [592]

I designed an entity data model with two entities between which there exists a many to many relationship. When I auto-generate SQL code to generate the database for this model, it has generated a table (two columns) to keep track of this many-to-many association. However, this table has a PRIMARY KEY NONCLUSTERED on both columns.

This is extremely annoying because I've to do manual workarounds to deal with this issue, when supposedly the sql generated by the EF is azure compatible.

Issue was already reported in stackoverflow.
http://stackoverflow.com/questions/3567946/entity-framework-many-to-many-clustered-vs-nonclustered-index

Can you please fix this with urgency?
Thanks