anchor.diff:  
   <p class="note"><strong>Note:</strong> This feature is only for apps that run on Linux Diego Cells. It does not work for apps that run on Windows Diego Cells.</p>
   
  -This topic describes how to administer dynamic egress policies for the apps in your deployment. 
  +This topic describes how to administer dynamic egress policies for the apps in your deployment.
   
   
   ## <a id="overview"></a> Overview
   
   You can create dynamic egress policies to allow your apps to communicate with external services, such as a MySQL database. The workflow is as follows:
   
  -* Create a destination object with details about the external service that your app or space need access to, including an IP range.   
  -* Create an egress policy from the app or space to the destination object. 
  +* Create a destination object with details about the external service that your app or space need access to, including an IP range.
  +* Create an egress policy from the app or space to the destination object.
   
   Dynamic egress policies provide the following benefits over App Security Groups (ASGs):
   
  -* You do not have to restart your apps when applying these policies, so there is no downtime. 
  +* You do not have to restart your apps when applying these policies, so there is no downtime.
   * The policies include an additional level of granularity: you can apply them to specific apps.
   
  -For more information about ASGs, see [App Security Groups](../concepts/asg.html). 
  -
  -
  -## <a id="enable"></a> Enable the Dynamic Egress Feature
  -
  -The dynamic egress feature is disabled by default. To enable this feature, you must 
  -<% if vars.platform_code == 'CF' %>
  -set the `enforce_experimental_dynamic_egress_policies` property of the `policy-server-internal` job to true. For more information, see the spec file in the [CF Networking Release](https://github.com/cloudfoundry/cf-networking-release/blob/develop/jobs/policy-server-internal/spec#L102-L104) repository. 
  -<p class="note"><strong>Note:</strong> This feature is only compatible with the Silk CNI plugin.</p>
  -<% else %>
  -<%=vars.enable_egress%>
  -<% end %>
  +For more information about ASGs, see [App Security Groups](../concepts/asg.html).
   
   
   ## <a id="auth"></a> API Authorization
  
positive.code: 
  ### <a id="cf-curl"></a> Option 1: cf curl
  
  When you use [cf curl](https://cli.cloudfoundry.org/en-US/cf/curl.html), you do not have to provide a token or the full API URL because you are already logged in and targeting your deployment. See the following example: 
  
  ```sh
  $ cf curl /networking/v1/external/egress_policies
  
negative.code: ### <a id="list-egress-policies"></a> List Egress Policies
  
  #### GET /networking/v1/external/egress_policies
  #### Arguments:
  
  None
  
  