anchor.diff:  }
   ```
   
  -The final step before enabling the SSO provider in Buildkite, is to perform a test login.
  -
  -Perform a test login via your SSO provider, or using the `url` returned from the update mutation.
  +### Step 4
  +
  +The final step before enabling the SSO provider in Buildkite, is to perform a test login. Perform a test login via your SSO provider, or using the `url` returned from the update mutation.
   
   Once a test login has been completed, you can do the final step: enabling the provider using the `ssoProviderEnable` mutation. Running this mutation will require all your users to login via your SAML provider before they can access your organization on Buildkite.
   
  
positive.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.
  
  
negative.code: ```
  
  ## Setting up G Suite
  
  ### Step 1
  
  The first step in setting up a G Suite SSO provider is to use the `ssoProviderCreate` mutation to create a new provider in your Buildkite organization:
  
  