anchor.diff:            <th>with the contents of this file&hellip;</th>
           </tr>
           <tr>
  -          <td><code>CC_MUTUAL_TLS_CA_CERT</code></td>
  +          <td><code>CC-MUTUAL-TLS-CA-CERT</code></td>
             <td><code>cf-diego-ca.crt</code></td>
           </tr>
           <tr>
  -          <td><code>CC_MUTUAL_TLS_PUBLIC_CERT</code></td>
  +          <td><code>CC-MUTUAL-TLS-PUBLIC-CERT</code></td>
             <td><code>cloud_controller.crt</code></td>
           </tr>
           <tr>
  -          <td><code>CC_MUTUAL_TLS_PRIVATE_KEY</code></td>
  +          <td><code>CC-MUTUAL-TLS-PRIVATE-KEY</code></td>
             <td><code>cloud_controller.key</code></td>
           </tr>
         </table>
  
positive.code: meta:
    environment: ENVIRONMENT
      </code></pre></td>
      <td>Replace <code>ENVIRONMENT</code> with an arbitrary name describing your environment, for example <code>azure-prod</code>.
      </td>
    </tr>
    <tr>
      <td><pre><code>
    reserved_static_ips:
    - CLOUD_FOUNDRY_PUBLIC_IP
      </code></pre></td>
      <td>Replace <code>CLOUD_FOUNDRY_PUBLIC_IP</code> with an existing public IP address for your Azure network. This is assigned to the <code>ha_proxy</code> job to receive incoming traffic.
      </td>
    </tr>
    <tr>
  
negative.code:   <tr>
      <td><pre><code>
    loggregator_endpoint:
      shared_secret: LOGGREGATOR-ENDPOINT-SHARED-SECRET
      </code></pre></td>
      <td>Replace <code>LOGGREGATOR-ENDPOINT-SHARED-SECRET</code> with a secure string that you generate.
      </td>
    </tr>
    <tr>
      <td><pre><code>
    nats:
      user: NATS-USER
      password: NATS-PASSWORD
      </code></pre></td>
      <td>Replace <code>NATS-USER</code> and <code>NATS-PASSWORD</code> with a username and secure password of your choosing. Cloud Foundry components use these credentials to communicate with each other over the NATS message bus.
        </td>
    </tr>
    <tr>
      <td><pre><code>
    router:
      status:
        user: ROUTER-USER
        password: ROUTER-PASSWORD
      </code></pre></td>
      <td>
        Replace <code>ROUTER-USER</code> and <code>ROUTER-PASSWORD</code> with a username and secure password of your choosing.
        </td>
    </tr>
    <tr>
      <td><pre><code>
    uaa:
      admin:
        client_secret: ADMIN-SECRET
      cc:
        client_secret: CC-CLIENT-SECRET
      clients:
        cc_service_key_client:
          secret: CC-SERVICE-KEY-CLIENT-SECRET
        cc_routing:
          secret: CC-ROUTING-SECRET
        cloud_controller_username_lookup:
          secret: CLOUD-CONTROLLER-USERNAME-LOOKUP-SECRET
        doppler:
          secret: DOPPLER-SECRET
        gorouter:
          secret: GOROUTER-SECRET
        tcp_emitter:
          secret: TCP-EMITTER-SECRET
        tcp_router:
          secret: TCP-ROUTER-SECRET
        login:
          secret: LOGIN-CLIENT-SECRET
        notifications:
          secret: NOTIFICATIONS-CLIENT-SECRET
        cc-service-dashboards:
          secret: CC-SERVICE-DASHBOARDS-SECRET
      </code></pre></td>
      <td>Replace the values for all <code>secret</code> keys with secure secrets that you generate. <br><br>You can configure container-to-container networking in this section. If you want to deploy container-to-container networking, see the <i>Enable on an IaaS</i> section of the <a href="../../devguide/deploy-apps/cf-networking.html#iaas">Administering Container-to-Container Networking</a> topic, beginning with step 4.
      </td>
  