anchor.diff:  mutation CreateProvider {
     ssoProviderCreate(input: {
       organizationId: "<organization id>",
  -    type: SAML
  +    type: SAML,
  +    emailDomain: "myorg.com",
  +    emailDomainVerificationAddress: "admin@myorg.com"
     }) {
       ssoProvider {
         state
  
positive.code: 
  You should now see that the provider’s state is enabled.
  
  See the `SSOProviderUpdatePayload` documentation for other properties that can be configured on your SSO provider, such as `sessionDurationInHours` and `note`.
  
  ## Setting up SAML (Okta, OneLogin, ADFS and others)
  
  
negative.code: 
  The next step is to log into your SSO provider’s system and setup Buildkite using the `issuer`, `ssoURL` and `metadata` returned above. Once setup, your SSO provider should provide a metadata URL that you can give to Buildkite.
  
  Using the metadata URL returned from your SSO provider, run the `ssoProviderUpdate` mutation to have Buildkite automatically retrieve the details and set it up, ready for a test login. This will not yet affect any of your Buildkite users.
  
  ```graphql
  mutation UpdateProviderMetaData {
  