I'm confused about Salesforce's direction on setting up a many-to-many relationship between Accounts and addresses.
Typically, a many-to-many relationship requires a junction object between the two primary objects (which would keep the data normalized).
However, looking at the standard objects in my org's schema, I'm seeing (1) some (standard) address fields on the Account object, (2) a separate (standard) Address object (with no direct connection to the Account object) and (3) a 'Location' object, that has a Master-Detail with Address, but only a Lookup relationship with Accounts(??)
Bottom line: Which method does SF recommend when your org has many Accounts per Address, and many possible Addresses for each Account? (Note: My org is using both Person Accounts and Business Accounts, for the 'right' reasons)