In this case, it seems that the main issue was a left over cookie which was interfering with Edge’s protocol handler process to detect WorkspaceApp installation.
In this case, it seems that the main issue was a left over cookie which was interfering with Edge’s protocol handler process to detect WorkspaceApp installation.