title: Using Azure AD as a identity provider for AWS
body: <p>We are trying to use Azure Active Directory as a Identity Provider for the Amazon AWS console but we are failing miserably!</p>
  
  <p>We have tried both the "Amazon Web Services (AWS)" and "AWS Console" applications in Azure, but they both produce the following error when someone tries to use either application to access AWS:</p>
  
  <p>"Your request did not include a SAML response"</p>
  
  <p>We've followed the steps in the following article to create an identity provider in AWS:
  <a href="http://blogs.aws.amazon.com/security/post/Tx71TWXXJ3UI14/Enabling-Federation-to-AWS-using-Windows-Active-Directory-ADFS-and-SAML-2-0" rel="nofollow">http://blogs.aws.amazon.com/security/post/Tx71TWXXJ3UI14/Enabling-Federation-to-AWS-using-Windows-Active-Directory-ADFS-and-SAML-2-0</a></p>
  
  <p>We used the following URL to upload the metadata for the identity provider in AWS:
  https:// login.windows.net//FederationMetadata/2007-06/FederationMetadata.xml</p>
  
  <p>We are using the following URL when we configure the application in Azure AD:
  https:// signin.aws.amazon.com/saml</p>
  
  <p>Using Fiddler we can see that nothing is being posted to the Amazon endpoint URL, the browser is just being redirected there without posting anything.</p>
  
  <p>Has anyone managed to get this working, we are struggling to see what we have missed so any help/advice will be very much appreciated.</p>
  
  <p>EDIT: We have also used the SAML tracer Add-On for Firefox to troubleshoot this, which shows nothing is being posted at all.  There is a GET request to account.activedirectory.windowsazure.com, which is followed by another GET request to signin.aws.amazon.com</p>