Modelling a second level table relationship
I recently answered a question just like this one here: 

How to structure Tables with changing status without duplicating data

You have two options, create the foreign key from Orders using both the AddressId and CustomerId or remove the CustomerId entirely from the Orders table as you can obtain it through the relation anyway.