anchor.diff:  
   ### <a id="update-policy"></a> Update an Egress Policy When an IP Changes
   
  -To update a policy, you update the destination. To update the destination of a policy: 
  +To update a policy, you update the destination. To update the destination of a policy:
   
   1. List all egress destinations to find the one you want to change. For more information, see [List Egress Destinations](#list-egress-destinations).
   
  
positive.code: ### <a id="list-egress-policies"></a> List Egress Policies
  
  #### GET /networking/v1/external/egress_policies
  #### Arguments: 
  
  None
  
  
negative.code: 
  <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.
  
  
  ## <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.
  
  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.
  * 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="auth"></a> API Authorization
  