Assuming this is a newer version of Umbraco above v10, then changing the backoffice path from /umbraco is no longer supported and restricting logins should be done in other ways (eg IP restrictions). There are some people who have suggested they have managed to work around this still by using URL Rewrites (rather than redirects), but I haven't personally tested this, it's not in any way officially supported, and it probably just gets added in addition to the original URL rather than replacing.
There's a long running github issue about the decision and all the reasons for it, as well as details of some people's attempted workarounds here:-
How to change default backoffice url
We have developed website using Umbraco CMS from Visual Studio 2022.
Website is running properly and all changes done from backoffice also reflected in preview and published mode.
Now we want to change default backoffice url from "/umbraco" to other like "/backoffice". Also we want to change favicon for backoffice login page.
Is it possible to change it ? if Yes then How to change it ?
Thanks Bhushan
We worked around this by redirecting from /backoffice to /umbraco
It doesn't hide the word 'umbraco' entirely since it shows up in the address bar after the redirect, but at least our designers don't have to type it
If you're interested in that here are the details
We did this by adding a reserved path so that umbraco didn't respond with a 404 on requests for '/backoffice'
in appsettings
Then added a controller called backoffice that redirects to umbraco
No this will not work, because we want to restrict all logins to backoffice from "/umbraco" url.
Our admin team only able to access the backoffice from "/backoffice" url.
So to stop backoffice working from "/umbraco" would be preferred.
Thanks Bhushan
Assuming this is a newer version of Umbraco above v10, then changing the backoffice path from /umbraco is no longer supported and restricting logins should be done in other ways (eg IP restrictions). There are some people who have suggested they have managed to work around this still by using URL Rewrites (rather than redirects), but I haven't personally tested this, it's not in any way officially supported, and it probably just gets added in addition to the original URL rather than replacing.
There's a long running github issue about the decision and all the reasons for it, as well as details of some people's attempted workarounds here:-
https://github.com/umbraco/Umbraco-CMS/issues/12593
is working on a reply...