OKTA-610875 Deprecate Zones API VuePress Reference (#4160)

* deprecate zones api and link updates

* Update packages/@okta/vuepress-site/docs/reference/api/zones/index.md

Co-authored-by: vanngo-okta <80703015+vanngo-okta@users.noreply.github.com>

---------

Co-authored-by: vanngo-okta <80703015+vanngo-okta@users.noreply.github.com>

Author: brianduffield-okta

packages/@okta/vuepress-site/conductor.yml

@@ -496,7 +496,7 @@ redirects:
   - from: /docs/api/resources/users/index.html
     to: /docs/reference/api/users/
   - from: /docs/api/resources/zones/index.html
-    to: /docs/reference/api/zones/
+    to: https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/
   - from: /docs/how-to/add-user-consent-to-flow/index.html
     to: /docs/guides/request-user-consent/
   - from: /docs/how-to/byo_saml/index.html
@@ -802,7 +802,7 @@ redirects:
   - from: /docs/api/resources/users
     to: /docs/reference/api/users/
   - from: /docs/api/resources/zones
-    to: /docs/reference/api/zones/
+    to: https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/
   - from: /docs/api/resources/social_authentication
     to: /docs/guides/social-login/
   - from: /docs/api/resources/social_authentication/index.html
@@ -900,7 +900,7 @@ redirects:
   - from: /docs/api/resources/trusted-origins.html
     to: /docs/reference/api/trusted-origins/
   - from: /docs/api/resources/zones.html
-    to: /docs/reference/api/zones/
+    to: https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/
   - from: /guides/add-saml-idp/-/configure-oidc-client/index.html
     to: /docs/guides/add-saml-idp/-/configure-oidc-client/
   - from: /guides/add-saml-idp/-/configure-saml-idp/index.html

packages/@okta/vuepress-site/docs/guides/archive-configure-signon-policy/main/index.md

@@ -67,7 +67,7 @@ The following are step-by-step instructions to configure an Okta sign-on policy
 
 3. For this use case example, leave the default of **Anywhere** in the **If User's IP is** drop-down box. For other use cases where you want to assign location parameters, you can specify what kind of location prompts authentication, for example, prompting a user for a factor when they aren't on the corporate network.
 
-    > **Note:** You can click the **Networks** link to access the gateway settings that enable your choice of access. A [network zone](https://help.okta.com/okta_help.htm?id=ext_Security_Network) is a security perimeter used to limit or restrict access to a network based on a single IP address, one or more IP address ranges, or a list of geolocations. You can also create networks zones using the [Zone API](/docs/reference/api/zones/).
+    > **Note:** You can click the **Networks** link to access the gateway settings that enable your choice of access. A [network zone](https://help.okta.com/okta_help.htm?id=ext_Security_Network) is a security perimeter used to limit or restrict access to a network based on a single IP address, one or more IP address ranges, or a list of geolocations. You can also create networks zones using the [Zone API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/).
 
 4. Leave the default of **Any** in the **And Authenticates via** drop-down box.
 

packages/@okta/vuepress-site/docs/guides/configure-signon-policy/main/index.md

@@ -130,7 +130,7 @@ The following are step-by-step instructions to configure another rule for the de
 
 4. Configure IF conditions to define the authentication context for the rule. Select **Not in any of the following zones** from the **AND User’s IP is** dropdown list.
 
-    > **Note:** You can click the **Go to Network Zones** link to access the gateway settings that enable your choice of access. A [network zone](https://help.okta.com/okta_help.htm?id=ext_Security_Network) is a security perimeter used to limit or restrict access to a network based on a single IP address, one or more IP address ranges, or a list of geolocations. You can also create network zones using the [Zones API](/docs/reference/api/zones/).
+    > **Note:** You can click the **Go to Network Zones** link to access the gateway settings that enable your choice of access. A [network zone](https://help.okta.com/okta_help.htm?id=ext_Security_Network) is a security perimeter used to limit or restrict access to a network based on a single IP address, one or more IP address ranges, or a list of geolocations. You can also create network zones using the [Zones API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/).
 
 5. In the text box, start typing the dynamic zone name and then select it when it appears in the list.
 

packages/@okta/vuepress-site/docs/reference/api/policy/index.md

@@ -1061,7 +1061,7 @@ Specifies an authentication entry point
 
 #### Network Condition object
 
-Specifies a network selection mode and a set of network zones to be included or excluded. If the connection parameter's data type is `ZONE`, one of the include or exclude arrays is required. Specific zone IDs to include or exclude are enumerated in the respective arrays. You can use the [Zones API](/docs/reference/api/zones/) to manage network zones.
+Specifies a network selection mode and a set of network zones to be included or excluded. If the connection parameter's data type is `ZONE`, one of the include or exclude arrays is required. Specific zone IDs to include or exclude are enumerated in the respective arrays. You can use the [Zones API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/) to manage network zones.
 
 | Parameter  | Description            | Data Type          | Required                               |
 | ---------  | ---------------------- | ------------------ | -------------------------------------- |

packages/@okta/vuepress-site/docs/reference/api/system-log/index.md

@@ -270,7 +270,7 @@ When an event is triggered by an HTTP request, the client object describes the [
 | id                  | For OAuth requests, this is the ID of the OAuth [client](https://tools.ietf.org/html/rfc6749#section-1.1) making the request. For SSWS token requests, this is the ID of the agent making the request. | String                                                    | TRUE     |
 | userAgent           | The [user agent](https://en.wikipedia.org/wiki/User_agent) that is used by an actor to perform an action                                                                                                      | [UserAgent object](#useragent-object)                     | TRUE     |
 | geographicalContext | The physical location where the client is making its request from                                                                                                                                          | [GeographicalContext object](#geographicalcontext-object) | TRUE     |
-| zone                | The `name` of the [Zone](/docs/reference/api/zones/#ZoneModel) that the client's location is mapped to                                                                                                | String                                                    | TRUE     |
+| zone                | The `name` of the [Zone](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/#tag/NetworkZone/operation/getNetworkZone) that the client's location is mapped to                                                                                                | String                                                    | TRUE     |
 | ipAddress           | IP address that the client is making its request from                                                                                                                                                      | String                                                    | TRUE     |
 | device              | Type of device that the client operates from (for example, Computer)                                                                                                                                          | String                                                    | TRUE     |
 

packages/@okta/vuepress-site/docs/reference/api/threat-insight/index.md

@@ -14,7 +14,7 @@ In order to prevent abuse, Okta ThreatInsight works in a limited capacity for fr
 | Field Name     | Description                                                         	| Data Type                                     | Required      | Max Length    |
 | :------------- | :------------------------------------------------------------------	| :-------------------------------------------- | :------------ | :------------ |
 | action         | Specifies how Okta responds to authentication requests from suspicious IPs. Values are none, audit, or block. A value of none indicates that ThreatInsight is disabled. A value of audit indicates that Okta logs suspicious requests in the System Log. A value of block indicates that Okta logs suspicious requests in the System Log and blocks the requests. | String                                        | Yes		| N/A           |
-| excludeZones   | Accepts a list of [Network Zone](/docs/reference/api/zones/) IDs. IPs in the excluded Network Zones aren't logged or blocked by Okta ThreatInsight and proceed to Sign On rules evaluation. This ensures that traffic from known, trusted IPs isn't accidentally logged or blocked. | List	                                        | No		| N/A           |
+| excludeZones   | Accepts a list of [Network Zone](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/) IDs. IPs in the excluded Network Zones aren't logged or blocked by Okta ThreatInsight and proceed to Sign On rules evaluation. This ensures that traffic from known, trusted IPs isn't accidentally logged or blocked. | List	                                        | No		| N/A           |
 
 
 ## ThreatInsight configuration API operations

packages/@okta/vuepress-site/docs/reference/api/zones/index.md

@@ -4,6 +4,12 @@ category: management
 ---
 # Zones API
 
+The Zones API reference is now available at the new [Okta API reference portal](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/) as the Network Zones API.
+
+Explore the [Okta Public API Collections](https://www.postman.com/okta-eng/workspace/okta-public-api-collections/overview) workspace to get started with the Network Zones API Postman collection.
+
+
+<!-- {api content}
 The Okta Zones API provides operations to manage Zones in your organization. There are two usage Zone types: Policy Network Zones and Blocklist Network Zones. Policy Network Zones are used to guide policy decisions. Blocklist Network Zones are used to deny access from certain IP addresses, locations, proxy types, or Autonomous System Numbers (ASNs) before policy evaluation.
 
 A default system Policy Network Zone is provided in your Okta org. You can use the Zones API to modify the default Policy Network Zone or to create a custom Policy or Blocklist Network Zone. When you create your custom Zone, you can specify if the Zone is an IP Zone or a Dynamic Zone. An IP Zone allows you to define network perimeters around a set of IPs, whereas a Dynamic Zone allows you to define network perimeters around location, IP type, and ASNs.
@@ -886,3 +892,4 @@ curl -X PUT \
   }
 }
 ```
+-->

packages/@okta/vuepress-site/docs/release-notes/2017/index.md

@@ -69,7 +69,7 @@ This parameter allows you to force the validation of the password policy's `minA
 
 The following bug fixes will be available on preview orgs starting Dec 13, 2017, and will be available on production orgs starting December 19, 2017:
 
-* When using the [Zones API](/docs/reference/api/zones/#update-a-network-zone), erasing all IP addresses in the Default IP Blocklist zone caused an error. (OKTA-145602)
+* When using the [Zones API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/#tag/NetworkZone/operation/replaceNetworkZone), erasing all IP addresses in the Default IP Blocklist zone caused an error. (OKTA-145602)
 
 
 ## 2017.49
@@ -483,7 +483,7 @@ Dates for preview and production release are the earliest possible release date.
 
 Zones are used to group IP Address ranges so that policy decisions can be made based on the client's IP location.
 
-[The Zones API](/docs/reference/api/zones/) is an <ApiLifecycle access="ea" /> release. Contact [Support](https://support.okta.com/help/open_case) to enable it.
+[The Zones API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/) is an <ApiLifecycle access="ea" /> release. Contact [Support](https://support.okta.com/help/open_case) to enable it.
 This API can be enabled beginning August 22, 2017 for preview orgs, and beginning September 5, 2017 for production orgs.
 
 ### API Bug Fix
@@ -529,7 +529,7 @@ You can also create an OpenID Connect app more easily with this simplified flow:
 
 Zones are used to group IP Address ranges so that policy decisions can be made based on the client's IP location.
 
-[The Zones API](/docs/reference/api/zones/) is an <ApiLifecycle access="ea" /> release. Contact [Support](https://support.okta.com/help/open_case) to enable it.
+[The Zones API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/) is an <ApiLifecycle access="ea" /> release. Contact [Support](https://support.okta.com/help/open_case) to enable it.
 This API can be enabled beginning August 22, 2017 for preview orgs, and beginning September 5, 2017 for production orgs.
 
 ### API Bug Fixes
@@ -1577,7 +1577,7 @@ The Zones API is now Generally Available in preview orgs. It will be at least on
 
 Zones are used to group IP Address ranges so that policy decisions can be made based on the zone a client's IP belongs to.
 
-For more information, see [the Zones API developer documentation](/docs/reference/api/zones/).
+For more information, see [the Zones API developer documentation](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/).
 
 > Update: Zones API is [a Beta release](/docs/reference/releases-at-okta/). This release note is in error.
 
@@ -1980,7 +1980,7 @@ Instead, Okta will send a customer communication explaining the migration path t
 
 ### Platform Feature Improvement: Zones API Generally Available in Preview
 
-Access policies can now be defined based on an IP address range using [the Zones API](/docs/reference/api/zones/).
+Access policies can now be defined based on an IP address range using [the Zones API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/).
 This feature is Generally Available in preview orgs for at least one month before being Generally Available in production. <!-- OKTA-121280 -->
 
 ### Platform Bugs Fixed

packages/@okta/vuepress-site/docs/release-notes/2018/index.md

@@ -253,7 +253,7 @@ The following features have already been released as Early Access. To enable the
 
 #### Bugs Fixed in 2018.40
 
-* Responses from the `/zones` [endpoint](/docs/reference/api/zones/#zones-api) included a duplicate of the `type` field. (OKTA-188605)
+* Responses from the `/zones` [endpoint](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/) included a duplicate of the `type` field. (OKTA-188605)
 * The `/idps/credentials/keys` [endpoint](/docs/reference/api/idps/#add-x509-certificate-public-key) was requiring requests to include extra parameters. (OKTA-189780)
 
 #### Previously Released Early Access Features 2018.40 Update
@@ -525,7 +525,7 @@ The following features have already been released as Early Access. To enable the
 
 #### Bugs Fixed in 2018.29
 
-* Using the [Zones API](/docs/reference/api/zones/) to modify an existing zone that is blocked, removed the zone from the blocklist and converted it to a normal IP Zone. (OKTA-176610)
+* Using the [Zones API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/) to modify an existing zone that is blocked, removed the zone from the blocklist and converted it to a normal IP Zone. (OKTA-176610)
 * Using the [Applications API](/docs/reference/api/apps/) to create an OAuth client caused an error if the `credentials.oauthClient` property was not provided, even though it is not required. (OKTA-179275)
 * The System Log CSV report did not contain a value for `AuthenticationContext.issuer` for the event type `user.authentication.authenticate`. (OKTA-147165)
 
@@ -591,7 +591,7 @@ The [System Log API](/docs/reference/api/system-log/) is now Generally Available
 #### Bugs Fixed in 2018.27
 
 * Users who clicked an Activation Link for an [Okta Verify factor](/docs/reference/api/factors/#activate-push-factor) that had already been activated would get back an HTTP 500 error. (OKTA-146511)
-* Attempting to add more than the maximum number of zones via the [Zones API](/docs/reference/api/zones/) would result in an HTTP 500 error. (OKTA-175991)
+* Attempting to add more than the maximum number of zones via the [Zones API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/) would result in an HTTP 500 error. (OKTA-175991)
 
 #### Previously Released Early Access Features 2018.27 Update
 

packages/@okta/vuepress-site/docs/release-notes/2019/index.md

@@ -351,7 +351,7 @@ The Okta Mappings API provides operations to manage the mapping of properties be
 
 #### Missing type property now returns a 400 error code
 
-If you create an [IP network zone](/docs/reference/api/zones/#ip-zone-properties) without a `type` property for an IP field, PUT or POST requests made to the Zone API now return a 400 error code. <!-- OKTA-239170 -->
+If you create an [IP network zone](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/) without a `type` property for an IP field, PUT or POST requests made to the Zone API now return a 400 error code. <!-- OKTA-239170 -->
 
 #### Bug Fixed in 2019.08.0