Windows Azure services infrastructure allows you to deploy all kinds of different roles, You can build great applications with SharePoint but they may not be ready for platform-as-service . The great part of windows Azure is ability to deploy the applications as software as service without writing any code. This post outlines the steps to deploy the SharePoint application to windows azure.
1. First create a configuration for deploying the virtual mission
The parameters are name of the virtual machine, AvailabilitySetName and ImageName and InstanceSize. The pipeline in the script tells command to send the output to the next line.
2. Adding the provisioning configuration for unattended xml file which contains the information about what the machine should do when it is comes out from generalized to specialized state. You are basically specifying the parameters that you find in the unattended xml file.
You can specify the domain name and user credentials and attached domain and joining domain.
3. The next step is what end point that you want to expose so you can create the VM and the end point at same time
In this case you are creating endpoint on port 80 and also going to create a load balance set with specific name and then specify probepath that is basically going to check a test page. This probepath helps you to check whether the load balance server is alive or not.
The above three steps effectively a one power shell command which you can repeat for creating every new virtual machine.
4. Finally specify the DNS name and then it actually create VMs on live
| Share this post : |  |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
