Atlas ConneX Issue - Editing a URL via Connex will put the workspace in a "Failed Editing" state

Below is a work-around which can be supplied to fix any workspace in this 'Failed Editing' state. 

Correcting Atlas SQL DB data impacted by the Workspace URL issue detected in Atlas 4.0

1. Accessing the Altas Database:

Go to https://portal.azure.com. In Azure Portal, navigate to the Resource Groups and, in the list, click on the Atlas resource group:




You will see the Overview window, containing a list of all the resources that are located in the resource group. Click on one of the function apps like the one named “func-atlas-wsf-XXX-prod”.

In the Function App, in the left menu, click on “Configuration” and scroll all the way down to the bottom to see the “Connection Strings” section with one variable, click on the name of the variable called “AtlasConnexContext”.

or in newer displays of Azure go to Settings > Environment variables > Connection strings tab

In this window, in the “Value” field, you can see a list of parameters separated by semicolons (;). Scroll to the right until you see the “User ID” and “Password” parameters. This password is the password of the database, so copy it to access the database.

Once the password is obtained, you can access the SQL database. The name of the database, in the resource group, is "sqldb-atlas-XXX-prod". Go to the "Query Editor" app in the left menu.

Take into account that if this is the first time, you will probably get rejected because your IP is not registered in the SQL Server. This is expected and in the same error message in the login page there is a link to include your IP in the SQL Server. Once you have clicked on that link, you can login again.

2. Updating the Database:

Once inside the database, we need to get the Workspace ID affected by this issue before making any changes. To do so, we can either right-click on the "Workspaces" (workspaces.Workspaces) table and select top 1000 rows and use the Search box in the results table or run the following query in the editor:



or running this query (note that the URL is the old one because that is what the database is incorrectly storing):

SELECT TOP (1000) * FROM [dbo].[Workspaces]
WHERE AssociatedSite_AbsoluteUrl like '%EndpointSecurityTeam_dw%'

Now, we need to copy the ID of the workspace.



With the ID of the affected Workspace we need to fix, we can now run the following query against the same Workspaces table:

UPDATE Workspaces
SET AssociatedSite_AbsoluteUrl = 'https://YOURTENANTNAME.sharepoint.com/sites/is_es_dw', Status = 2
where Id = '524C2F7D-BFAC-4068-9C59-6C2C8A1A9D23' -- REPLACE THIS ID BY THE ONE YOU COPIED BEFORE

NOTES:

Please ensure the 'UPDATE Workspaces is related to your table name. If you type ahead you will be able to select the correct one

Please make sure the URL in this query is the actual correct one needed.

Please REPLACE the ID by the one you copied before. The ID in the snippet is just an example.

If the query is succeeded, the Database is now corrected.

3. Updating navigation term URL in Taxonomy.

In case this workspace was being referenced in a navigation term in the Term Store, please make sure to manually update it according to the actual URL of the Workspace.

4. Waiting for the Function Apps Sync

Once all above is done, the only pending task is waiting until the Azure Function App synchronizes the Database and the Search Services so ConneX can display the updated information in the ConneX form. This process is periodically triggered and it shouldn't take more than an hour.

With this, the issue should be fixed.