dimanche 1 février 2015

Alternate access mapping for Azure internet-published SharePoint site, remains redundant redirect to *.cloudapp.net

Hi I have SharePoint portal in Azure, that I try to connect to my custom domain address.


I created and assigned static VIP to machine. Extended my Sharepoint application to internet zone, example mysite.cloudapp.net, set up it to use FBA authentication. Azure gives public name to machine so I accessed my site from internet via this address(by example "http://ift.tt/1CnzmWO"). All works.


Now I bought domain, created CNAME and A records few days ago, and added this address to Alternate Access Mappings in my SharePoint. By example it will be "http://MySP.com"


So alternate access mappings now are like this:


enter image description here



It works. But now if I type http://MySP.com, it changes in my browser to http://ift.tt/1CnzmWO. I don't want this, I want user to see only http://MySP.com(or http://www.MySP.com) header.


So I made backup and decided to delete http://ift.tt/1CnzmWO from AAM. After this if I type http://MySP.com I see in fiddler that there begins a loop and site does not open. I added it back but anyway got this loop. So now I restored and don't know - how to set up http://MySP.com address for this Azure SharePoint portal correctly?


I read this article, but it does not explain how to create two external addresses with no redirects http://ift.tt/15xRP5B


Aucun commentaire:

Enregistrer un commentaire