Remove refs to Appliance

Remove references

Fix links

Fix redirects

Author: Katie Horne

STYLEGUIDE.md

@@ -191,4 +191,4 @@ For general software-industry styles and terminology, see the [Microsoft Writing
 * Tenant: a logical isolation unit of the products we offer. Examples of Auth0 tenants: `foo.auth0.com`, `bar.auth0.com`
 * Auth0 tenants: regular cloud tenants
 * Subscription: a contract or service plan. Examples of subscriptions: trial, free, developer or developer-pro
-* Private instances: appliance instances
+* Private Cloud/Managed Private Cloud: single-tenant deployments

WORDS.md

@@ -39,10 +39,10 @@ When writing about tokens, capitalize specific token names as follows:
 * Access Token
 * Refresh Token
 
-#### Within Appliance subscriptions
+#### Within Private Cloud subscriptions
 
 * **Auth0 tenants** refers to regular cloud tenants
-* **Private instances** refers to appliance instances
+* **Private Cloud** or **Managed Private Cloud** refers to single-tenant deployments
 
 ### TL;DR
 

articles/api/management/v2/changes.md

@@ -76,7 +76,7 @@ This document describes the major differences between Auth0's Management API v1
 | [GET /api/connections/{connection}/users?search={criteria}](/api/v1) | None. | [GET  /api/v2/users](/api/v2#!/Users/get_users) (see note) |
 
 ::: note
-For PSaaS Appliance (search_engine:v1), use `connection` field; for cloud (search_engine:v2), use `q=identities.connection:"connection_name"`
+For Private Cloud (search_engine:v2), use `q=identities.connection:"connection_name"`
 :::
 
 ### Rules endpoints

articles/appliance/disaster-recovery-raci.md

@@ -126,7 +126,7 @@ The following table details the task division for configuring, creating, and mon
             <td>Restore the Data Backup</td>
             <td>R, C</td>
             <td>I</td>
-            <td>Please open a ticket in the <a href="${env.DOMAIN_URL_SUPPORT}">Auth0 Support Center</a> to request assistance with restoring a backup. Auth0 Customer Success Engineers will review your request, and if necessary, partner with the subscriber's infrastructure engineers to restore the environment. Please note that, in certain cases, a <a href="/services/private-saas-configuration">Professional Services</a> fee may apply.</td>
+            <td>Please open a ticket in the <a href="${env.DOMAIN_URL_SUPPORT}">Auth0 Support Center</a> to request assistance with restoring a backup. Auth0 Customer Success Engineers will review your request, and if necessary, partner with the subscriber's infrastructure engineers to restore the environment. Please note that, in certain cases, a <a href="/services/private-cloud-configuration">Professional Services</a> fee may apply.</td>
         </tr>
     </tbody>
 </table>

articles/applications/guides/enable-third-party-applications.md

@@ -23,7 +23,7 @@ If you use Lock in the [Hosted Login Page](/hosted-pages/login), you must:
 
 - Upgrade to Lock version 10.7.x or later
 - Set the `__useTenantInfo: config.isThirdPartyClient` flag when instantiating Lock
-- *For [PSaaS Appliance](/appliance) users only*: Set the [`configurationBaseUrl` option](https://github.com/auth0/lock#other-options) to `https://{config.auth0Domain}/` when instantiating Lock
+- *For [Private Cloud](/private-cloud) users only*: Set the [`configurationBaseUrl` option](https://github.com/auth0/lock#other-options) to `https://{config.auth0Domain}/` when instantiating Lock
 
 ### Sample script:
 

articles/compliance/gdpr/features-aiding-compliance/protect-user-data.md

@@ -93,12 +93,26 @@ For details see [Step-up Authentication](/multifactor-authentication/step-up-aut
 
 Auth0 is designed and built as a scalable, highly available, multi-tenant cloud service. We are highly resilient to the failure of any of our components, because we  implement redundant components at all levels. We also detect failures rapidly and our failover is very quick. 
 
-We support four deployment models:
-
-- A **multi-tenant cloud service** running on Auth0's cloud
-- A **dedicated cloud service** running on Auth0's cloud
-- A **dedicated cloud service** running on Customer's cloud infrastructure
-- An **on-premises virtual [Private SaaS (PSaaS) Appliance](/appliance)** running on Customer's private environment (for the cases where a public cloud-based solution is not acceptable).
+We support three deployment models:
+
+<table class="table">
+<tr>
+    <th>Deployment</th>
+    <th>Description</th>
+</tr>
+<tr>
+    <td>Public Cloud</td>
+    <td>A multi-tenant cloud service running on Auth0's cloud</td>
+</tr>
+<tr>
+    <td>Private Cloud</td>
+    <td>A dedicated cloud service running on Auth0's cloud</td>
+</tr>
+<tr>
+    <td>Managed Private Cloud</td>
+    <td>A dedicated cloud service running on either Auth0's cloud or the customer's AWS cloud infrastructure</td>
+</tr>
+</table>
 
 You decide which deployment model works best for you based on your business and security requirements.
 

articles/connector/troubleshooting.md

@@ -85,9 +85,9 @@ When the domain does not exist or is unreachable `nltest` will return an error m
 
 ### UNABLE_TO_VERIFY_LEAF_SIGNATURE error message
 
-This error applies to the AD/LDAP Connector in combination with the PSaaS Appliance.
+This error applies to the AD/LDAP Connector in combination with the Private Cloud.
 
-When the connector will fail to start if unable to validate the SSL certificate configured in the PSaaS Appliance. This can happen when the Root Certificate (or any Intermediate Certificates) are missing in the machine's Certificate Store (Windows). In order to solve this you should import the certificate chain in the **Local Machine > Trusted Root** certificate store on the machine where the AD/LDAP Connector is installed.
+When the connector will fail to start if unable to validate the SSL certificate configured in the Private Cloud. This can happen when the Root Certificate (or any Intermediate Certificates) are missing in the machine's Certificate Store (Windows). In order to solve this you should import the certificate chain in the **Local Machine > Trusted Root** certificate store on the machine where the AD/LDAP Connector is installed.
 
 ### Running the connector behind a proxy
 

articles/custom-domains/index.md

@@ -9,16 +9,16 @@ useCase: customize-domains
 ---
 # Custom Domains
 
-::: warning
-PSaaS Appliance customers should see [this page](/appliance/custom-domains) for information on using custom domains.
-:::
-
 Auth0 allows you to map the domain for your tenant to a custom domain of your choosing. This allows you to maintain a consistent experience for your users by keeping them on your domain instead of redirecting or using Auth0's domain.
 
 For example, if your Auth0 domain is **northwind.auth0.com**, you can have your users to see, use, and remain on **login.northwind.com**.
 
 It is recommended that you use custom domains with Universal Login for the most seamless and secure experience for your end users. Check the [Universal Login documentation](/hosted-pages/login) to see if your plan and use case support custom domains. 
 
+::: warning
+Private Cloud customers should see [this page](/appliance/custom-domains) for information on using custom domains.
+:::
+
 ## Prerequisites
 
 * This feature is not available for free plans. To configure a custom domain you have to [upgrade your account to any paid plan](${manage_url}/#/tenant/billing/subscription)

articles/email/templates.md

@@ -72,7 +72,7 @@ See [Configuring the Redirect To URL](#configuring-the-redirect-to-url) for more
 Users will see the sender's address in the **From Address** field when receiving an email from Auth0. If you do not configure a **From Address** for your emails your emails will be sent from the email address of the first owner of your Auth0 account.
 
 ::: note
-For security purposes, you may not send customized emails from any `@auth0.com` address. If you are a PSaaS Appliance user, you may configure a similar domain blacklist.
+For security purposes, you may not send customized emails from any `@auth0.com` address. If you are a Private Cloud user, you may configure a similar domain blacklist.
 :::
 
 The **From Address** field supports all the [common variables](#common-variables) for templates, but these are the most commonly used:

articles/extensions/delegated-admin/v2/index.md

@@ -15,10 +15,6 @@ useCase: extensibility-extensions
 
 The **Delegated Administration** extension allows you to grant a select group of people administrative permissions to the [Users page](${manage_url}/#/users) without providing access to any other area. This is done by exposing the [Users Dashboard](${manage_url}/#/users) as an Auth0 application.
 
-:::panel PSaaS Appliance Availability
-The Delegated Administration extension is available for [PSaaS Appliance](/appliance) customers who are running build `10755` or later, and have User Search enabled.
-:::
-
 Prior to configuring the extension, you will need to:
 
 * [Create and configure an Auth0 Application](#create-an-application)

articles/extensions/delegated-admin/v3/index.md

@@ -17,10 +17,6 @@ The **Delegated Administration** extension allows you to grant a select group of
 
 Follow this tutorial to learn how to expose the Users dashboard to a group of users without allowing them access to the rest of the management dashboard. 
 
-:::panel PSaaS Appliance Availability
-The Delegated Administration extension is available for [PSaaS Appliance](/appliance) customers who are running build `10755` or later, and have User Search enabled.
-:::
-
 Prior to configuring the extension, you will need to:
 
 * [Create and configure an Auth0 Application](#create-an-application)

articles/extensions/user-import-export.md

@@ -11,10 +11,6 @@ useCase: extensibility-extensions
 ---
 # User Import / Export
 
-::: note
-The User Import / Export extension is available in the PSaaS Appliance beginning with version `10755` when you have user search enabled.
-:::
-
 The **User Import / Export Extension** allows you to:
 
 * Bulk import your existing database users into Auth0

articles/getting-started/the-basics.md

@@ -55,10 +55,10 @@ In our example, `Example-Co` picked the name `example-co` and Americas as their
 
 We recommend the use of custom domains, such as `example-co.com`, in your production environments to provide your users with the most secure and seamless experience. This comes with an additional cost. 
 
-If you have a **single-tenant** implementation, you can deploy your custom domain in one of three locations:
+If you have a [**single-tenant** implementation](/private-cloud), you can deploy your custom domain in:
+
 - The cloud managed by Auth0
-- A cloud managed by you
-- An [on-premise installation](/appliance)
+- An AWS cloud managed by you
 
 For more information, see [Custom Domains](/custom-domains). 
 

articles/monitoring/_includes/_monitor-appliance.md

@@ -0,0 +1,3 @@
+::: panel Monitor a dedicated deployment
+See the [Private Cloud](/private-cloud) documentation for information on [monitoring](/appliance/monitoring) a dedicated deployment.
+:::

articles/monitoring/_includes/_monitor-private-cloud.md

@@ -58,7 +58,7 @@ Here is an example call to the `/testall` endpoint:
 
 If all services are up, the endpoint returns the `200` HTTP response code and a simple text message of `OK`. If any service is down, it returns a `5xx` response code.
 
-<%= include('../_includes/_monitor-appliance.md') %>
+<%= include('../_includes/_monitor-private-cloud.md') %>
 
 ## Keep reading
 

articles/monitoring/guides/test-testall-endpoints.md

@@ -15,7 +15,7 @@ useCase:
 
 You can monitor your Auth0 implementation and Auth0 status and services, as well as send logging event data to third-party tools.
 
-<%= include('./_includes/_monitor-appliance.md') %>
+<%= include('./_includes/_monitor-private-cloud.md') %>
 
 ## Check availability and status
 

articles/monitoring/index.md

@@ -116,8 +116,8 @@ To speed resolution, please provide the following when logging an issue:
 * Screenshot of error message (if any)
 * HTTP trace in the form of a [.har file](/har)
 
-*For PSaaS Appliance Customers*:
+*For Private Cloud Customers*:
 
-* PSaaS Appliance version/build number (top left hand corner of configuration screen on config tenant, such as https://yourmanage.yourdomain.com/configuration#/)
+* Private Cloud version/build number (top left hand corner of configuration screen on config tenant, such as https://yourmanage.yourdomain.com/configuration#/)
 * Status of nodes (https://yourmanage.yourdomain.com/configuration#/nodes)
 * Status of health check (https://yourmanage.yourdomain.com/configuration#/troubleshoot)

articles/onboarding/enterprise-support.md

@@ -12,7 +12,7 @@ useCase:
 
 # Data Transfer Policy
 
-At this time, Auth0 will not transfer data from one Auth0 tenant to another. This applies to both Cloud and PSaaS Appliance customers.
+At this time, Auth0 will not transfer data from one Auth0 tenant to another. This applies to both Public Cloud and Private Cloud customers.
 
 All data in your Auth0 tenant is always under your control and is [available through the Management API](/api/v2) at any time. The only information which is not available through the API are the password hashes of your [Auth0-hosted database users](/connections/database) and private keys, for security reasons.
 

articles/policies/data-transfer.md

@@ -37,9 +37,9 @@ Auth0 requires that:
 * You disclose any suspected findings to the Auth0 Security team for explanation/discussion
 * You understand that your tenant will be moved between environments during testing. Auth0 will move your tenant from the stable environment to the preview environment before the testing commences. Auth0 will then return your tenant to the stable environment once the testing period ends. Note that while your tenant is on the preview environment it may receive updates more rapidly.
 
-## PSaaS Appliance customers
+## Private Cloud customers
 
-Private SaaS Appliance customers should also request permission to run a penetration test via the [Auth0 support center](${env.DOMAIN_URL_SUPPORT}). Please include the [information listed above](/policies/penetration-testing#information-required) with your support request.
+Private Cloud customers should also request permission to run a penetration test via the [Auth0 support center](${env.DOMAIN_URL_SUPPORT}). Please include the [information listed above](/policies/penetration-testing#information-required) with your support request.
 
 ## Load testing
 

articles/policies/penetration-testing.md

@@ -32,7 +32,7 @@ useCase:
 
 <%= include('../_includes/_topic-links', { links: [
   'services/pair-programming',
-  'services/private-saas-configuration',
+  'services/private-cloud-configuration',
   'services/code-review'
 ] }) %>
 
@@ -41,5 +41,5 @@ useCase:
 <%= include('../_includes/_topic-links', { links: [
   'services/auth0-introduction',
   'services/auth0-advanced',
-  'services/private-saas-management'
+  'services/private-cloud-management'
 ] }) %>

articles/services/index.md

@@ -2,7 +2,7 @@
 description: A project to assist with design and deployment of a Private SaaS Auth0 environment.
 topics:
   - professional services
-  - psaas-appliance
+  - private-cloud
   - design
   - deployment
   - configuration

articles/services/private-saas-configuration.md articles/services/private-cloud-configuration.md

@@ -2,7 +2,7 @@
 description: A workshop designed to provide IT organizations with core Auth0 Private SaaS management concepts.
 topics:
   - professional services
-  - psaas-appliance
+  - private-cloud
   - management
 contentType:
   - reference

articles/services/private-saas-management.md articles/services/private-cloud-management.md

@@ -15,7 +15,7 @@ useCase:
 
 With [Support Center](${env.DOMAIN_URL_SUPPORT}), you can create tickets for questions or issues you are experiencing. You can access Support Center if you are a full administrator of an Auth0 account, or have received an invitation to Support Center from an administrator. 
 
-If you are an existing PSaaS Appliance customer, you will need to create an Auth0 cloud-based account to log in to the Support Center. This account can also be used for Dev/Test purposes at no additional cost. Please contact your Customer Success Manager or Sales Executive to associate your cloud-based account to your existing PSaaS Appliance subscription.
+If you are an existing Private Cloud customer, you will need to create an Auth0 cloud-based account to log in to the Support Center. This account can also be used for Dev/Test purposes at no additional cost. Please contact your Customer Success Manager or Sales Executive to associate your cloud-based account to your existing Private Cloud subscription.
 
 ## Open a new ticket
 
@@ -24,7 +24,7 @@ If you are an existing PSaaS Appliance customer, you will need to create an Auth
 1. Choose **Affected Tenant** from the dropdown menu.
 1. Under **Issue Type** select the type of issue that best fits your case.
 ![Issue types](/media/articles/support/issue-types.png)
-    * **Public Cloud Support Incident** or **Appliance Support Incident** - (the second option is only available to Appliance customers)
+    * **Public Cloud Support Incident** or **Private Cloud Support Incident** - (the second option is only available to Private Cloud customers)
         * If you are not a Trial Tenant customer, you will be asked to select a severity:
             * **Low: Product Question** - You have questions about how things work, whether we support something
             * **Normal: General Support Question** - You are in development and have a question about how to configure something or how to resolve an error

articles/support/tickets.md

@@ -32,7 +32,7 @@ In discussing user search, we use the following terms related to the search resu
 * **Immediately consistent**: The search results will reflect the results of all successful write operations, including those that occurred shortly prior to your request.
 
 ::: note
-User Search v3 is not available for the PSaaS Appliance.
+User Search v3 is not available for the Private Cloud.
 :::
 
 ## Keep reading

articles/users/search/v3/index.md

@@ -2089,6 +2089,14 @@ module.exports = [
     {
       from: '/enterprise/private-cloud/overview',
       to: '/private-cloud'
+    },
+    {
+      from: '/services/private-saas-configuration',
+      to: '/services/private-cloud-configuration'
+    },
+    {
+      from: '/services/private-saas-management',
+      to: '/services/private-cloud-management'
     }
 
 

config/redirects.js

@@ -265,7 +265,7 @@ articles:
         url: /onboarding/enterprise-support
 
       - title: Release Notes
-        url: https://auth0.com/changelog/appliance
+        url: https://auth0.com/releases/
         external: true
         forceFullReload: true
 
@@ -1171,7 +1171,7 @@ articles:
         url: "/services/pair-programming"
 
       - title: "Private SaaS reconfiguration"
-        url: "/services/private-saas-configuration"
+        url: "/services/private-cloud-configuration"
 
       - title: "Auth0 Introduction"
         url: "/services/auth0-introduction"
@@ -1180,7 +1180,7 @@ articles:
         url: "/services/auth0-advanced"
 
       - title: "Private SaaS Management Workshop"
-        url: "/services/private-saas-management"
+        url: "/services/private-cloud-management"
 
 apis: