Recently a customer wanted a new external Url for SharePoint (intranet.domain.com). I implemented it via Zones and alternate access mapping and so far it works fine. They also stopped using their internal url and use the intranet now everywhere.

Now it occured that users got emails whos links point to the internal SharePoint url instead of the external intranet url. It probably wouldn't be as much of a problem if there would not be a authentication problem with SharePoint and access via its internal (servername) url since some changes to the iis authentication methods.

I found a technet article which proposes a Cmdlet to update the urls of old Alerts and this is fine. But now I ask myself if new alerts might again use the internal url, or, if the site is only used via intranet, email links from new alerts will also use the intranet url.

Then I would also like to now what happens if I change the Default Zone to intranet[...]. Would this break SharePoint or is it a good idea (if the internal url isn't needed any more) to fix more of these "old urls used" problem?

Note: SharePoint 2010 is used

1 Answer 1


SharePoint uses the default URL for links in alerts and workflows that are automatically kicked off. Regarding alerts the only real way around this is to change the URL of the Default zone. This can be done in CA with the AAM, by the cmdlet Set-SPAlternateURL or (my preference) delete the web application (preserving the data of course) and creating a new web app to use your new URL. The option you select depends on how much configuration you have done to web apps and its authentication providers. The first two options might work for you but it really depends on how much configuration you have done after the web app was created. The only way to be sure nothing will break is to recreate the web app.

The TechNet article you reference is for a migrated web app that is still using the URL of the old environment and won't help you much here.

  • Ok that sounds promising, thank you. I will first try to change the default zone. I guess I don't need the Extranet zone anymore then? So there is no need for that conversion... If I change the default zone, all existing alerts will change too then?
    – Kirschi
    Commented Jan 20, 2014 at 15:12
  • I would switch the zone, if you are moving the Extranet zone to the Default zone, I would move the Default Zone to the Extranet zone or Custom zone. You really have no way of knowing 100% where SP is using the original Default zone of that web app.
    – Dovahkiin
    Commented Jan 20, 2014 at 15:15
  • Thank you! It seems to work, but do you have one more idea for Tasks assignment? The Email "Task has been assigned to you" still seems to have the old Url. Interestingly the "Task has been added" Email uses the new Url in all links. I am not sure if a custom Emailtemplate is used but I do not think so.
    – Kirschi
    Commented Jan 23, 2014 at 12:56
  • 1
    Could be the config DB still hanging on to the old URL or the email template didn't quite update. At this point it might be worht trying that TechNet article you referenced earlier. Again the only way to be certain the URLs will work corectly would be to delete and recreate the web app. Good Luck
    – Dovahkiin
    Commented Jan 23, 2014 at 13:49
  • 1
    This is fantastic. Just by changing the Default URL in AAM now the alerts sends me with the new URL that I was looking for. Thanks for your help.
    – user39574
    Commented Feb 12, 2015 at 1:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.