Cloud Services

Official Documentation

Service Description

Microsoft Azure Cloud Services are (in addition to Web Apps and Virtual Machines) one of three options for executing applications in the cloud. Cloud Services focus very strongly on highly available, highly scalable, multilayered Web applications that benefit most from the flexible resource provision of a public cloud. These applications can be divided into components, called "roles," that can be scaled independently of one another. Microsoft Azure handles the management of the virtual machines required to execute the roles. This includes upgrades to guest operating systems, patching, and failover (failed components are automatically replaced). Unlike with Web sites, developers have full administrative access to the virtual machines in order to, for example, install additional software in the individual instances. Remote Desktop connections for administration are also supported. Roles can be scaled independently of one another (addition or removal of instances); this operation can also be automated (depending on various load parameters) using the auto-scaling function.

Getting Started

  1. Cloud Services Learning Path
    9/27/2016, Webpage

Azure Documentation

1. Overview
     1.1. What is Cloud Services?
     1.2. Cloud service config files and packaging
2. Get Started
     2.1. Example .NET Cloud Service
     2.2. Example Python for Visual Studio Cloud Service
     2.3. Set up a hybrid HPC cluster with Microsoft HPC Pack
3. How To
     3.1. Plan
          3.1.1. Virtual machine sizes
          3.1.2. Updates
     3.2. Develop
          3.2.1. Create PHP web and worker roles
          3.2.2. Build and deploy a Node.js application
          3.2.3. Build a Node.js web application using Express
          3.2.4. Storage and Visual Studio
               3.2.4.1. Blob storage and connected services
               3.2.4.2. Queue storage and connected services
               3.2.4.3. Table storage and connected services
          3.2.5. Configure packages for continuous build and deploy
               3.2.5.1. Visual Studio Team Services and Git
               3.2.5.2. Visual Studio Team Services
               3.2.5.3. TFS and Team Build
          3.2.6. Configure traffic rules for a role
          3.2.7. Handle Cloud Service lifecycle events
          3.2.8. Socket.io (Node.js)
          3.2.9. Use Twilio to make a phone call (.NET)
          3.2.10. New Relic
          3.2.11. Configure start up tasks
               3.2.11.1. Create startup tasks
               3.2.11.2. Common startup tasks
               3.2.11.3. Use a task to Install .NET on a Cloud Service role
          3.2.12. Configure Remote Desktop
               3.2.12.1. Portal
               3.2.12.2. Classic portal
               3.2.12.3. PowerShell
     3.3. Deploy
          3.3.1. Create and deploy a cloud service in portal
               3.3.1.1. Portal
               3.3.1.2. Classic portal
          3.3.2. Create an empty cloud service container in PowerShell
          3.3.3. Configure a custom domain name
               3.3.3.1. Portal
               3.3.3.2. Classic portal
          3.3.4. Stage a cloud service deployment (Node.js)
          3.3.5. Connect to a custom Domain Controller
     3.4. Manage service
          3.4.1. Common management tasks
               3.4.1.1. Portal
               3.4.1.2. Classic portal
          3.4.2. Configure Cloud Service
               3.4.2.1. Portal
               3.4.2.2. Classic portal
          3.4.3. Manage a Cloud Service using Azure Automation
          3.4.4. Configure automatic scaling
               3.4.4.1. Portal
               3.4.4.2. Classic portal
          3.4.5. Use Python to manage Azure Resources
          3.4.6. Guest OS patches
          3.4.7. Guest OS retirement
               3.4.7.1. Retirement policy
               3.4.7.2. Family 1 retirement notice
          3.4.8. Guest OS release news
          3.4.9. Cloud Services Role config XPath cheat sheet
     3.5. Manage certificates
          3.5.1. Cloud Services and management certificates
          3.5.2. Configure SSL
               3.5.2.1. Portal
               3.5.2.2. Classic portal
     3.6. Monitor
          3.6.1. Monitor cloud service
          3.6.2. Test performance
               3.6.2.1. Test with Visual Studio Profiler
          3.6.3. Enable diagnostics
               3.6.3.1. PowerShell
               3.6.3.2. .NET
               3.6.3.3. Visual Studio
          3.6.4. Use performance counters in Azure Diagnostics
          3.6.5. Store and view diagnostic data in Azure Storage
          3.6.6. Trace Cloud Service with Diagnostics
          3.6.7. Send diagnostic data to App Insights
     3.7. Troubleshoot
          3.7.1. Debug
               3.7.1.1. Enable remote debugging with cont. delivery
               3.7.1.2. Options for a Cloud Service
               3.7.1.3. Local Cloud Service with Visual Studio
               3.7.1.4. Published Cloud Service with Visual Studio
          3.7.2. Cloud Service allocation failure
          3.7.3. Common causes of Cloud Service roles recycling
          3.7.4. Default TEMP folder size too small for role
          3.7.5. Common deployment problems
          3.7.6. Role failed to start
          3.7.7. Recovery guidance
          3.7.8. Cloud Services FAQ
               3.7.8.1. Application and service availability FAQ
               3.7.8.2. Configuration and management FAQ
               3.7.8.3. Connectivity and networking FAQ
               3.7.8.4. Deployment FAQ
4. Reference
     4.1. .csdef XMLSchema
     4.2. .cscfg XMLSchema
     4.3. REST
5. Resources
     5.1. Azure Roadmap
     5.2. Learning path
     5.3. MSDN forum
     5.4. Pricing
     5.5. Service updates
     5.6. Videos

Tools

Tool Description
CloudMonix CloudMonix enhances Microsoft Azure by providing deep monitoring of most of Azure's infrastructure via live dashboards, ability to self-heal from many different production issues, on-demand historical performance and uptime reports, customizable alerts & notifications, sophisticated auto-scaling engine, integration to third party systems, and a lot more.