> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/operate/maintain-and-change/authentication-migration.md). # Authentication migration Migrate AnywhereNow Authentication from the legacy auth.anywhere365.cloud platform to the current login.anywhere365.cloud platform. Some customers experienced intermittent authentication issues — for example, the login page incorrectly reporting users as already logged in — with the legacy AnywhereNow Authentication Service. This was resolved in bundle **DC2024.01f** with a new Microsoft Authentication Services backend. This guide describes how to migrate customers from the legacy `auth.anywhere365.cloud` platform to the current `login.anywhere365.cloud` platform. {% hint style="warning" %} Perform these steps **after** the bundle upgrade to DC2024.01f or higher has successfully completed. Both platforms remain operational during the upgrade window, but migration should be completed as soon as possible after the upgrade. {% endhint %} *** ## Before you start * Confirm the bundle upgrade to DC2024.01f or higher is complete. * Identify which Unified Contact Center (UCC) services have authentication enabled. * Confirm whether local application clients (Snapper, Inflight Wallboard) are in use — these require additional steps after migration. * Confirm who can view, edit, create, or delete authentication profiles in OnePortal for the customer. {% hint style="warning" %} Deleting or recreating an authentication profile can interrupt sign-in for WebAgent, Dialogue Studio, and other authentication-protected applications. Use the profile delete/recreate workflow only in an approved migration window with a rollback owner. {% endhint %} *** ## Method 1: Self-service migration (preferred) This method is performed entirely by the customer or partner using OnePortal (the Dialogue Cloud Neo administration portal used by partners and customers), and provides full control over timing and rollback. {% hint style="danger" %} **Service interruption**: disabling authentication in Step 1 immediately prevents users from signing in to WebAgent, Dialogue Studio, and all other authentication-protected AnywhereNow applications. Re-authentication is unavailable until Step 4 is complete and the new profile is active. The interruption typically takes 5–10 minutes but may vary depending on portal and request processing speed. **Schedule this during a maintenance window or low-traffic period.** Notify affected users before starting. {% endhint %} ### Step 1: Disable authentication on the service 1. In OnePortal, navigate to **Services** and locate the affected service. 2. Disable **AnywhereNow Authentication** for this service. 3. Wait for the request to reach **Completed** status in the **Requests** menu before proceeding. ### Step 2: Remove the authentication configuration 1. In OnePortal, delete the existing authentication configuration for this service. If the migration only requires maintaining a current profile, use the authentication profile-management view to update the display name, App ID, or app secret instead of deleting and recreating the profile. Confirm service impact before rotating the app secret on a live profile. ### Step 3: Update the redirect URL in Azure 1. In the [Azure App registrations portal](https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps), navigate to the App registration used for AnywhereNow Authentication. 2. On the **Authentication** tab, **replace** the existing redirect URL with the new URL: ``` https://login.anywhere365.cloud/auth/realms//broker/oidc/endpoint ``` Replace `` with the AnywhereNow Tenant ID. See [Configure Authentication — Add the redirect URL](/platform-administration/provisioning/provisioning/configurations/configure-authentication.md#add-the-redirect-url) for full details. ### Step 4: Create a new authentication profile in OnePortal 1. In OnePortal, create a new Authentication Profile using the updated redirect URL. 2. Authentication is enabled immediately and automatically applied across all affected web applications on the new platform. ### Step 5: Update local application clients (if applicable) See [After migration](#after-migration) below. *** ## Method 2: Coordinated migration with AnywhereNow Support Use this method if the customer or partner does not have full OnePortal access, or prefers AnywhereNow to coordinate the change. {% hint style="info" %} Coordinated changes cannot be scheduled on weekends. Availability is limited to CET business hours. {% endhint %} ### Step 1: Update the Azure redirect URL Before the migration window, update the Azure redirect URL to the new value: ``` https://login.anywhere365.cloud/auth/realms//broker/oidc/endpoint ``` See [Configure Authentication — Add the redirect URL](/platform-administration/provisioning/provisioning/configurations/configure-authentication.md#add-the-redirect-url). ### Step 2: Raise a support request Raise a request to the AnywhereNow Support team. Support creates a change request for the AnywhereNow Cloud Operations team. ### Step 3: Agree on migration date and time Customer, Support, and the AnywhereNow Cloud Operations team agree on a migration window. ### Step 4: Cloud Team runs the migration On the agreed date, the AnywhereNow Cloud Operations team runs the migration script that moves the customer's Authentication profile from the old platform to the new platform. ### Step 5: Remove the old redirect URL from Azure After the migration script completes, remove the old `auth.anywhere365.cloud` redirect URL from the Azure App registration. {% hint style="info" %} If the migration script can be scheduled outside customer business hours, the Azure URL change can be made in advance of the window. {% endhint %} ### Step 6: Update local application clients (if applicable) See [After migration](#after-migration) below. *** ## After migration ### Dialogue Studio, Web Wallboard, and Generic Dialogue Provider No manual configuration is required. These applications use the new redirect URL automatically after migration. ### Snapper Update the redirect URL in the Snapper client configuration to point to `login.anywhere365.cloud`. ### Inflight Wallboard Update the redirect URL in the `config.xml` file to point to `login.anywhere365.cloud`. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://atlas.anywhere.now/operate/maintain-and-change/authentication-migration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.