July 30

New Edge browser crashes if do search on address bar

UPDATE: Microsoft has fix this in the latest release, 84.0.522.59

The new Edge – version 84.0.522.49 –  will crash if you do a  search on address bar and have google.com as your search engine.
I changed to Bing as search engine and everything is fine.
I have reported this to Microsoft Edge team as feedback

NOTE: I am wondering if Microsoft did this on purpose 🙂

Category: SharePoint | Comments Off on New Edge browser crashes if do search on address bar
January 10

SharePoint Screen Apps

SharePoint Screen Apps are content editor web parts that connect to a text file that is really an html file.
That text file includes css & js to load up jquery, react, angularjs, bootstrap, and some special function used to assist in calling SharePoint Rest APIs.
This allows for any jquery (datatable.net, jslider, etc.) to be used on the page.

I am working on book that will detail this and have a CD of examples

 

Category: SharePoint | Comments Off on SharePoint Screen Apps
October 23

SharePoint 2013 On-Site vs Office 365 Cloud

So you have been tasked with choosing between in on-site vs cloud versions of SharePoint.
You have another choice and that is to do both also known as hybrid.

SharePoint 2013 features are the same on-site and in the cloud.

A Forrester Research Inc. survey of IT decision makers shows:

  • 62% (82% in 2010) plan to deploy SharePoint 2013 on-premises
  • 8% (4% in 2010) will do so in a Microsoft datacenter
  • 26% (5% in 2010) will deploy SharePoint in a hybrid mode, both on-premises and cloud

While that shows a clear majority plan to run SharePoint in-house, that number is down from 2010.

Metalogix Software Corporate Survey had similar findings, showing

  • 55% intend to continue running SharePoint entirely in-house
  • 10% plan to run it purely in the cloud.
  • 35% are planning hybrid SharePoint implementations.

Let us look at some business rules that would slant you one way or the other.

Business Rule On-Site Cloud
Company does not want information outside the premises X
Company has users over across multiple continent X
Company is involved in a lot of legal battles X
Company needs to interact with external clients X
Company wants to be use SharePoint as Order Entry System X
Company does not have IT Operational department personal to support SharePoint long term X
Need to connect SharePoint to on-site systems X
Company is moving everything to the “Cloud” X
Company does not have financial resources to take on yearly cloud membership fees X
Company want to increase their mobile access X

Security issues have caused a lot of companies to avoid the cloud. With all the security breaches in the news a lot these days, it easy to see why companies IT Security officers do want anything to do with any cloud based system.

The promise of reduced cost have a lot of company thinking about moving to the cloud, doing research on cloud benefits, or taking the plunge and moving to the cloud.

Comfort level with what you know has caused a lot to go with on-site implementation.

Areas which I have seen that influence the direction are: Comfort, Cost & Legal.
– If a company already has SharePoint on-site and they are upgrading to 2013, they tend to keep it on-site.
– If a company is looking to reduce infrastructure cost, they tend to go with a cloud based solution.
– If a company’s legal department want to control their intellectual properties and assets, they tend to keep it on-site

Category: SharePoint, SharePoint 2013 | Comments Off on SharePoint 2013 On-Site vs Office 365 Cloud
July 6

X-UA-Compatible meta tag

The X-UA-Compatible meta tag allows web authors to choose what version of Internet Explorer the page should be rendered as. IE11+ have changes to these modes. See IE11 note below. The IE Technical Preview, the version that will be released after IE 11, will only honor X-UA-Compatible meta tag in certain circumstances. See IE Technical Preview note below.

Here are your options:

  • “IE=edge”
  • “IE=10”
  • “IE=EmulateIE10”
  • “IE=9”
  • “IE=EmulateIE9
  • “IE=8”
  • “IE=EmulateIE8”
  • “IE=7”
  • “IE=EmulateIE7”
  • “IE=5”

To attempt to understand what each means here are definitions provided by Microsoft:
Internet Explorer supports a number of document compatibility modes that enable different features and can affect the way content is displayed:

  • IE10 mode provides the highest support available for established and emerging industry standards, including the HTML5, CSS3 and others.
  • IE9 mode provides the highest support available for established and emerging industry standards, including the HTML5 (Working Draft), W3C Cascading Style Sheets Level 3 Specification (Working Draft), Scalable Vector Graphics (SVG) 1.0 Specification, and others. [Editor Note: IE 9 does not support CSS3 animations].
  • IE8 mode supports many established standards, including the W3C Cascading Style Sheets Level 2.1 Specification and the W3C Selectors API; it also provides limited support for the W3C Cascading Style Sheets Level 3 Specification (Working Draft) and other emerging standards.
  • IE7 mode renders content as if it were displayed in standards mode by Internet Explorer 7, whether or not the page contains a directive.
  • Emulate IE9 mode tells Internet Explorer to use the directive to determine how to render content. Standards mode directives are displayed in IE9 mode and quirks mode directives are displayed in IE5 mode. Unlike IE9 mode, Emulate IE9 mode respects the directive.
  • Emulate IE8 mode tells Internet Explorer to use the directive to determine how to render content. Standards mode directives are displayed in IE8 mode and quirks mode directives are displayed in IE5 mode. Unlike IE8 mode, Emulate IE8 mode respects the directive.
  • Emulate IE7 mode tells Internet Explorer to use the directive to determine how to render content. Standards mode directives are displayed in Internet Explorer 7 standards mode and quirks mode directives are displayed in IE5 mode. Unlike IE7 mode, Emulate IE7 mode respects the directive. For many web sites, this is the preferred compatibility mode.
  • IE5 mode renders content as if it were displayed in quirks mode by Internet Explorer 7, which is very similar to the way content was displayed in Microsoft Internet Explorer 5.
  • Edge mode tells Internet Explorer to display content in the highest mode available. With Internet Explorer 9, this is equivalent to IE9 mode. If a future release of Internet Explorer supported a higher compatibility mode, pages set to edge mode would appear in the highest mode supported by that version. Those same pages would still appear in IE9 mode when viewed with Internet Explorer 9.

NOTE: As of Internet Explorer 10, quirks mode behaves differently than it did in earlier versions of the browser. In Windows Internet Explorer 9 and earlier versions, quirks mode restricted the webpage to the features supported by Microsoft Internet Explorer 5.5. In Internet Explorer 10, quirks mode conforms to the differences specified in the HTML5 specification.

IE 11

From Microsoft (here):
Starting with IE11, edge mode is the preferred document mode; it represents the highest support for modern standards available to the browser.

Use the HTML5 document type declaration to enable edge mode:

<!doctype html>

Edge mode was introduced in Internet Explorer 8 and has been available in each subsequent release. Note that the features supported by edge mode are limited to those supported by the specific version of the browser rendering the content.

Starting with IE11, document modes are deprecated and should no longer be used, except on a temporary basis. Make sure to update sites that rely on legacy features and document modes to reflect modern standards.

If you must target a specific document mode so that your site functions while you rework it to support modern standards and features, be aware that you’re using a transitional feature, one that may not be available in future versions.

If you currently use the x-ua-compatible header to target a legacy document mode, it’s possible your site won’t reflect the best experience available with IE11.

IE Technical Preview

Information on X-UA-Compatible meta tag for the next version of IE. From Microsoft(here):
Introducing the “living” Edge document mode

As we announced in August 2013, we are deprecating document modes as of IE11. With our latest platform updates, the need for legacy document modes is primarily limited to Enterprise legacy web apps. With new architectural changes, these legacy document modes will be isolated from changes in the “living” Edge mode, which will help to guarantee a much higher level of compatibility for customers who depend on those modes and help us move even faster on improvements in Edge. The next major version of IE will still honor document modes served by intranet sites, sites on the Compatibility View list, and when used with Enterprise Mode only.

Public Internet sites will be rendered with the new Edge mode platform (ignoring X-UA-Compatible). It is our goal that Edge is the “living” document mode from here out and no further document modes will be introduced going forward.

Chrome=1 Info for IE

There is also chrome=1 that you can use or use together with one of the above options, EX: <meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1"> chrome=1 is for Google’s Chrome Frame which is defined as:
Google Chrome Frame is an open source browser plug-in. Users who have the plug-in installed have access to Google Chrome’s open web technologies and speedy JavaScript engine when they open pages in the browser.

Google Chrome Frame seamlessly enhances your browsing experience in Internet Explorer. It displays Google Chrome Frame enabled sites using Google Chrome’s rendering technology, giving you access to the latest HTML5 features as well as Google Chrome’s performance and security features without in any way interrupting your usual browser usage.

When Google Chrome Frame is installed, the web just gets better without you having to think about it.
But for that plug-in to work you must use chrome=1 in the X-UA-Compatible meta tag.

More info on Chrome Frame can be found here.

Note: Google Chrome Frame was retired on February 25, 2014. More info can be found here. Thank You @mck for the link.

Validation:

HTML5:

The page will validate using the W3 Validator only when using <meta http-equiv="X-UA-Compatible" content="IE=Edge">. For other values it will throw the error: A meta element with an http-equiv attribute whose value is X-UA-Compatible must have a content attribute with the value IE=edge. In other words, if you have IE=edge,chrome=1 it will not validate. I ignore this error completely as modern browsers simply ignore this line of code.

Category: SharePoint | Comments Off on X-UA-Compatible meta tag
July 23

Creating SharePoint 2013 Azure

Create SharePoint 2013 in Azure

The instructions on how to do this, Build SP2013 in the Cloud, are not up-to-date. So I have updated them.
Word version of this here

Change  [XYZ] to your initials, in my case JDH

Create Azure Affinity Group

  1. Selecting Settings
  2. Click the +ADD button on the bottom navigation bar
  3. Name: Enter a unique name for your new Affinity Group, such as [XYZ]NET01-AG
    Region:
  4. Select Networks located on the side navigation panel on the Windows Azure Management Portal page.
  5. Click the +NEW button located on the bottom navigation bar and select Networks | Virtual Network | Register DNS Server.
  6. Complete the DNS Server fields as follows:
    NAME: [XYZ]SER2012
    DNS Server IP Address: 10.0.0.4
  7. Click the REGISTER DNS SERVER button.
  8. Select Networks located on the side navigation panel on the Windows Azure Management Portal page.
  9. Click the +NEW button located on the bottom navigation bar and select Networks | Virtual Network | Quick Create.
  10. Complete the Virtual Network fields as follows:
    NAME: [XYZ]NET001
    Address Space: 10.—.—.—
    Maximum VM Count: 4096 [CIDR: /20] – Affinity Group: [XYZ]NET01-AG
    Connect to Existing DNS: Select XXXlabdns01 – the DNS Server registered in Exercise 1 above.
  11. Click the CREATE A VIRTUAL NETWORK button.

Register DNS

  1. Select Networks located on the side navigation panel on the Windows Azure Management Portal page.
  2. Click the +NEW button located on the bottom navigation bar and select Networks | Virtual Network | Register DNS Server.
  3. Complete the DNS Server fields as follows:
    NAME: [XYZ]SER2012
    DNS Server IP Address: 10.0.0.4
  4. Click the REGISTER DNS SERVER button

Create Virtual Network

  1. Select Networks located on the side navigation panel on the Windows Azure Management Portal page.
  2. Click the +NEW button located on the bottom navigation bar and select Networks | Virtual Network | Quick Create.
  3. Complete the Virtual Network fields as follows:
    NAME: [XYZ]NET001
    Address Space: 10.—.—.—
    Maximum VM Count: 4096 [CIDR: /20] – Affinity Group: [XYZ]NET01-AG
    Connect to Existing DNS: Select XXXlabdns01 – the DNS Server registered in Exercise 1 above.
  4. Click the CREATE A VIRTUAL NETWORK button.

Create and Configure a Windows 2012 Server in a Windows Azure VM

Create Windows 2012 VM

  1. Select Virtual Machines located on the side navigation panel on the Windows Azure Management Portal page.
  2. Click the +NEW button located on the bottom navigation bar and select Compute | Virtual Machines | From Gallery.
  3. In the Virtual Machine Operating System Selection list, select Windows Server 2012 Datacenter and click the button.
  4. On the Virtual Machine Configuration page, complete the fields as follows:
    Version Release Date: Select the latest version release date to build a new VM with the latest OS updates applied.
    Virtual Machine Name: [XYZ]SER2012
    New User Name: Choose a secure local Administrator user account to provision.
    New Password and Confirm Password fields: Choose and confirm a new local Administrator password.
    Size: Small (1 core, 1.75GB Memory)
    Click the check button.
  5. On the Virtual Machine Mode page, complete the fields as follows:
    Cloud Service: Create new cloud service
    Cloud Service DNS Name: [XYZ]SPCLOUD.cloudapp.net
    Region/Affinity Group/Virtual Network: [XYZ]NET001
    – Virtual Network Subnets: Select Subnet-1 (10.0.0.0/23)
    – Storage Account: Use an Automatically generated storage account
    Click the button to continue.
  6. On the Virtual Machine Mode page, complete the fields as follows:
    Availability Set: Create new availability set
    Availability Set Name: [XYZ]AVAILSET01
    – Enable PowerShell Remoting: Checked
  7. Click the check button to continue.

VERIFY IP Address

  1. On the virtual machine Dashboard page for [XYZ]SER2012, make note of the Internal IP Address displayed on this page located on the right-side of the page. This IP address should be listed as 10.0.0.4. If not, then delete [XYZ]SER2012 and start over at step 1

Attach Data Disk

  1. On the virtual machine Dashboard page for [XYZ]SER2012, click the Attach button located on the bottom navigation toolbar and select Attach Empty Disk. Complete the following fields on the Attach an empty disk to the virtual machine form:
    Name: [XYZ]SER2012-data01
    Size: 10 GB
    Host Cache Preference: None
  2. Click the button to create and attach the a new virtual hard disk
  3. On the virtual machine Dashboard page for [XYZ]SER2012, click the Connect button located on the bottom navigation toolbar and click the Open button to launch a Remote Desktop Connection to the console of this virtual machine. Logon at the console of your virtual machine with the local Administrator credentials defined above.
  4. On Server Manager Screen, select File and Storage Services, then Disks.
  5. Right-Click on 10G Unknown partition and select New Volume….
  6. Press Next
  7. Press Next
  8. Press OK
  9. Verify Drive letter is F: and then press Next
  10. Change Volume Label to DATA then press Next
  11. Press Create button

Install Active Directory Domain Services

  1. On Server Manager Dashboard Screen, on right side of screen, select Manage->Add role and Feature
  2. Press Next
  3. Select Role-based or Feature-based installation if it is not already selected and press Next
  4. Make sure server [XYZ]SER2012 is selected and press Next
  5. Check Active Directory Domain Service and then press Add Features on window that pops up.
  6. Press Next
  7. Press Next
  8. Check Restart destination server automatically if needed
  9. Press Yes to question
  10. Press Install

Make Server Domain Controller

  1. On Server Manager Dashboard Screen, press flag on right side (it should have orange trangle under it)
  2. Select Promote this server to domain controller link.
  3. Select Add a new forest radio button
    Domain : [XYZ].com
  4. Select Add a new forest radio button then Press Next
  5. Type in passwords for recovery then Press Next
  6. Press Next
  7. Change all the paths from C:\… to F:\… then Press Next
  8. Press Next
  9. Press Install

NOTE: You will be disconnected once install is done so VM can be rebooted. After disconnected, wait 2-3mins for reboot and reconnect.

Add SharePoint Service Accounts

  1. On Server Manager Dashboard Screen, select Tools->Active Directory Users and Computers
  2. Select your domain ([XYZ].com)
  3. Right-click on Users and select New->User and add following:
    [XYZ]\sp_farm – SharePoint Farm Data Access Account
    [XYZ]\sp_serviceapps – SharePoint Farm Service Applications Account
    [XYZ]\sp_user – SharePoint End User
    NOTE: Set password to never expire
  4. Close Active Directory Users and Computers

Setup and Configure SQL Server 2012 in a Windows Azure VM

Create SQL 2012 Server

  1. Select Virtual Machines located on the side navigation panel on the Windows Azure Management Portal page.
  2. Click the +NEW button located on the bottom navigation bar and select Compute | Virtual Machines | From Gallery.
  3. In the Virtual Machine Operating System Selection list, select SQL Server 2012 SP1 Enterprise on WIN2012 and click the button.
  4. On the Virtual Machine Configuration page, complete the fields as follows:
    Virtual Machine Name: [XYZ]SQL2012
    New User Name: Choose a secure local Administrator user account to provision.
    New Password and Confirm Password fields: Choose and confirm a new local Administrator password.
    Size: Medium (2 cores, 3.5GB Memory)
    Click the button to continue.
  5. On the Virtual Machine Mode page, complete the fields as follows:
    Cloud Service: [XYZ]SPCLOUD
    Region/Affinity Group/Virtual Network: Select [XYZ]NET01
    Virtual Network Subnets: Select Subnet-1 (10.0.0.0/23)
    Storage Account: Select Store Created above
  6. Click the button to continue.
  7. On the Next page, complete the fields as follows:
    Availability Set: [XYZ]AVAILSET01
    – Enable PowerShell Remoting: Checked
  8. Click the check button to continue.

 

VERIFY IP Address

  1. On the virtual machine Dashboard page for [XYZ]SQL2012, make note of the Internal IP Address displayed on this page located on the right-side of the page. This IP address should be listed as 10.0.0.5. If not, then delete [XYZ]SQL2012 and start over at step 1

Attach Data Disk

  1. On the virtual machine Dashboard page for [XYZ]SQL2012, click the Attach button located on the bottom navigation toolbar and select Attach Empty Disk. Complete the following fields on the Attach an empty disk to the virtual machine form:
    Name: [XYZ]SQL2012-data01
    Size: 50 GB
    Host Cache Preference: None
  2. Click the button to create and attach the a new virtual hard disk
  3. On the virtual machine Dashboard page for [XYZ]SQL2012, click the Connect button located on the bottom navigation toolbar and click the Open button to launch a Remote Desktop Connection to the console of this virtual machine. Logon at the console of your virtual machine with the local Administrator credentials defined above.
  4. On Server Manager Screen, select File and Storage Services, then Disks.
  5. Right-Click on 50G Unknown partition and select New Volume….
  6. Press Next
  7. Press Next
  8. Press OK
  9. Verify Drive letter is F: and then press Next
  10. Change Volume Label to DATA then press Next
  11. Press Create button
  12. Press Close button once finished

Change SQL Data Paths

  1. On F:\ Drive
    -Create folders
    F:\MSSQL
    F:\MSSQL\DATA
    F:\MSSQL\LOGS
    F:\MSSQL\BACKUP
  2. Open SQL Server Management Studio from Start | All Programs | Microsoft SQL Server 2012 | SQL Server Management Studio
  3. Connect to the SQL Server 2012 default instance using your Windows Account
  4. Right-click on your SQL Server instance and select Properties
  5. Select Database Settings from the left side pane
  6. Locate the Database default locations section and update the default values for each path to point to the new folder paths defined above
  7. Close SQL Server Management Studio.

Add Inbound Firewall
NOTE: In order to allow SharePoint to connect to the SQL Server, you will need to add
an Inbound Rule for the SQL Server requests in the Windows Firewall.

  1. Open Windows Firewall with Advanced Security
  2. On Server Manager Dashboard Screen, select Tools->Windows Firewall with Advanced Security
  3. In the Rule Type page, select Port and click Next
  4. In Protocols and Ports page, leave TCP selected, select Specific local ports, and set its value to 1433. Click Next to continue.
  5. In the Action page, make sure that Allow the connection is selected and click Next.
  6. In the Profile page, leave the default values and click Next.
  7. In the Name page, set the Inbound Rule’s Name to SQLServerRule and click Finish
  8. Close Windows Firewall with Advanced Security window.

Join to domain

  1. On Server Manager Dashboard Screen, select Local Server on the left
  2. Click on Workgroup name
  3. Click Change… button
  4. Select Domain radio button
  5. Enter your domain, i.e. [XYZ].com
  6. Press Ok
  7. Enter in Username/Password for admin
  8. Press OK
  9. Press OK
  10. Answer Yes to reboot

Give sp_farm user SQL sysadmin role

  1. Open SQL Server Management Studio from Start | All Programs | Microsoft SQL Server 2012 | SQL Server Management Studio
  2. Connect to the SQL Server 2012 default instance using your Windows Account
    NOTE: You may have to login in as .\ your windows account, since domain was added after install
  3. Add [XYZ]\sp_farm as sysadmin

Setup and Configure SQL SharePoint 2012 in a Windows Azure VM

Create SharePoint 2012 Server

  1. Select Virtual Machines located on the side navigation panel on the Windows Azure Management Portal page.
  2. Click the +NEW button located on the bottom navigation bar and select Compute | Virtual Machines | From Gallery.
  3. In the Virtual Machine Operating System Selection list, select SharePoint Server 2013 Trail and click the button.
  4. On the Virtual Machine Configuration page, complete the fields as follows:
    Version Release Date: Select the latest version release date to build a new VM with the latest OS updates applied.
    Virtual Machine Name: [XYZ]SP2013
    New User Name: Choose a secure local Administrator user account to provision.
    New Password and Confirm Password fields: Choose and confirm a new local Administrator password.
    Size: Small (4 core, 7GB Memory)
    Click the button.

VERIFY IP Address

  1. On the virtual machine Dashboard page for [XYZ]SP2013, make note of the Internal IP Address displayed on this page located on the right-side of the page. This IP address should be listed as 10.0.0.6. If not, then delete [XYZ]SP2013and start over at step 1

 

Join to domain

  1. On the virtual machine Dashboard page for [XYZ]SQL2012, click the Connect button located on the bottom navigation toolbar and click the Open button to launch a Remote Desktop Connection to the console of this virtual machine. Logon at the console of your virtual machine with the local Administrator credentials defined above
  2. On Server Manager Dashboard Screen, select Local Server on the left
  3. Click on Workgroup name
  4. Click Change… button
  5. Select Domain radio button
  6. Enter your domain, i.e. [XYZ].com
  7. Press Ok
  8. Enter in Username/Password for admin
  9. Press OK
  10. Press OK
  11. Answer Yes to reboot
  12. On the Virtual Machine Mode page, complete the fields as follows:
    Cloud Service: [XYZ]SPCLOUD
    Region/Affinity Group/Virtual Network: [XYZ]NET001
    – Virtual Network Subnets: Select Subnet-1 (10.0.0.0/23)
    – Storage Account: Use one created already
    Click the button to continue.
  13. On the Virtual Machine Mode page, complete the fields as follows:
    Availability Set: Create new availability set
    Availability Set Name: [XYZ]AVAILSET01
    – Enable PowerShell Remoting: Checked
  14. Click the button checkto continue.

VERIFY IP Address

  1. On the virtual machine Dashboard page for [XYZ]SP2013, make note of the Internal IP Address displayed on this page located on the right-side of the page. This IP address should be listed as 10.0.0.6. If not, then delete [XYZ]SP2013 and start over at step 1

Create SharePoint 2013 Farm

  1. On the Desktop, double-click on the SharePoint 2013 Products Configuration Wizard shortcut to launch the configuration wizard.
  2. Click the Next button to continue.
  3. If prompted to start or reset services, click the Yes button.
  4. In the SharePoint Products Configuration Wizard, when prompted on the Connect to server farm dialog,
    Select the option to Create a new server farm.
  5. On the Specify Configuration Database Settings, specify the following values for each field:
    – Database Server: [XYZ]SQL2012
    – Username: [XYZ]\sp_farm
    – Password: Type the password specified when the sp_farm domain user account was created earlier
    NOTE: If you cannot connect to database server, then log into [XYZ]SQL2012 and turn off Firewall
  6. Click the Next button
  7. Enter Paraphrase for farm
  8. Click the Next button
  9. Change Port to 55555
  10. Click the Next button
  11. Click the Next button
  12. Click the Finish button when prompted to complete the wizard
  13. Take default on IE Network question and press OK

Create Top level Site on SharePoint 2013 Farm

  1. Press Start Wizard button on How do you want to configure your SharePoint farm? screen
  2. In Service Account select Create new managed account
    User: [XYZ]\sp_serviceapps
  3. Press Next
  4. On the Create a Site Collection page, create a new top-level Intranet site collection using the following field values:
    Title and Description: Publishing
    URL: Select the root URL path – http://[XYZ]SP2013/
    Select experience version: 2013
    Select a template: Publishing | Publishing Portal
  5. Click the OK button to provision a new top-level Intranet site collection.

Verify Top level Site on SharePoint 2013 Farm

  1. After the new top-level Intranet site collection is provisioned, test navigating to the URL for this site collection from within the Remote Desktop session to the server.
    – http://[XYZ]SP2013/

Change Alternative Access mapping to use cloud url

  1. On the SharePoint 2013 Central Administration site, configure a Public URL alternate access mapping for accessing the new top-level Intranet site collection from the Internet.
  2. On the Central Administration site home page, click the Configure alternate access mappings link.
  3. On the Alternate Access Mappings page, click the Edit Public URLs link.
  4. On the Edit Public Zone URLs page, select and specify the following values:
    Alternate Access Mapping Collection: SharePoint – 80
    Internet: http://[XYZ]SPCLOUD.cloudapp.net
  5. Click the Save button
  6. On the SharePoint 2013 Central Administration site, configure a Public URL alternate access mapping for Central Admin.
  7. On the Central Administration site home page, click the Configure alternate access mappings link.
  8. On the Alternate Access Mappings page, click the Edit Public URLs link.
  9. On the Edit Public Zone URLs page, select and specify the following values:
    Alternate Access Mapping Collection: Central Administration – 55555
    Internet: http://[XYZ]SPCLOUD.cloudapp.net:55555
  10. Click the Save button

Configure Cloud Endpoints to point to SharePoint VM

  1. Sign in at the Windows Azure Management Portal with the logon credentials.
  2. Select Virtual Machines located on the side navigation panel on the Windows Azure Management Portal page.
  3. On the Virtual Machines page, click on the name of the SharePoint virtual machine – [XYZ]SP2013.
  4. On the [XYZ]SP2013 virtual machine details page, click on Endpoints in the top navigation area of the page.
  5. Click the +Add Endpoint button in the bottom navigation bar of the page.
  6. On the Add an endpoint to a virtual machine form, select the Add Endpoint option and
  7. Click the button to continue.
  8. On the Specify the details of the endpoint form, specify the following field values:
    Name: WebHTTP
    Protocol: TCP
    Public Port: 80
    Private Port: 80
  9. Click the button.
  10. After the endpoint configuration has been successfully applied, test browsing to the following public URL to confirm that you are able to access the Intranet site collection that is configured on SharePoint:
    URL: http://[XYZ]SPCLOUD.cloudapp.net
  11. Now add endpoint for central admin, On the Specify the details of the endpoint form, specify the following field values:
    Name: CentralAdmin
    Protocol: TCP
    Public Port: 55555
    Private Port: 55555
  12. Click the button
  13. After the endpoint configuration has been successfully applied, test browsing to the following public URL to confirm that you are able to access the Intranet site collection that is configured on SharePoint:
    URL: http://[XYZ]SPCLOUD.cloudapp.net:55555