Download RightScale

Listed in the marketplace, but that application is used for SSO, not for cloud management integration.The only way to add this today is to go through the cloud registration process through RightScale as specified above.The ARM user performing this step must be a member of the Active Directory Tenant containing the subscription (not a guest).After registration, the only permission that the RightScale Service Principal will have on the Azure AD tenant is Sign-in and read user profile.Grant RightScale permission to a subscriptionIn order for RightScale to be able to manage cloud resources, it must have permissions granted on the Subscriptions in Azure. The RightScale cloud registration process will automatically add the RightScale service principal to the specified subscription with the Contributor role -- this is the required role for RightScale to have in order to perform cloud management on Azure.While this permission can be manually granted in AD, the RightScale cloud registration steps must still be followed in order to associate the RightScale account with the correct subscription.The user performing this action must have the Owner role on the Subscription.After registration, the RightScale Service Principal will have Contributor access on the Subscription.Grant RightScale read access to a subscriptionIn order to provide RightScale read access to a subscription, you need to first follow the steps under Connect Microsoft Azure Resource Manager to your RightScale Account.Once the AzureRM subscription has successfully been registered to the RightScale account, you can then restrict its access by following these steps:Go to the Subscriptions blade in the AzureRM Portal.Select the Subscription you would like to modify access for.Go to Access Control (IAM)Find the RightScale user and remove it.Re-add the RightScale user by selecting Add, choose Reader for the role, and find the RightScale application user in the directory.Save your changes.

Launch-Initial BootWhen launching a new server (with a ServerTemplate and MultiCloudImage (MCI)) the following steps occur:The MCI and/or Server have tags that specify how the RightScale platform should produce user-data (see also cloud-init info):typically the rs_agent:type=right_link_lite tag specifies multi-part mime user-data and will include RightLink 10 appropriate parametersif RightLink 10 is not installed on the image, then typically a rs_agent:mime_include_url= tag is used to have cloud agent download and execute the RightLink 10 installerIf the instance was launched via RightScale Cloud Appliance for vSphere (RCA-V), networking is configured.The instance boots and an agent reads and acts on the user-data and metadata. On Linux, this agent is typically cloud-init while on Windows the situation is more complicated. For now, RightLink comes with a service to read userdata, detailed in Userdata Retrieval on Windows section below.The first user-data script places the instance parameters into /var/lib/rightscale-identity (Linux) or C:\ProgramData\RightScale\RightLink\rightscale-identity (Windows).The optional second script installs RightLink 10, which includes the following steps:creates a 'rightlink' (Linux) and 'RightLink' (Windows) user for the rightlink serviceinstalls sudoers config for the 'rightlink' user (Linux only)downloads the RightLink 10 archivedetermines the type of init system (systemd, upstart, or sysvinit) and installs the appropriate startup scripts (Linux) or NSSM is used to install RightLink as a service (Windows)starts the RightLink 10 serviceensures that the user-data based user scripts (the two scripts discussed here) run on every bootThe RightLink 10 service starts and authenticates with the platform, it then:retrieves the boot bundle and executes itif all scripts in the boot bundle

May check the status of your cloud. Both of these items must be valid and active (green) in order to successfully launch cloud servers:On the Dashboard, go to Settings > Account Settings > Clouds. You should be able to view all the Azure Resource Manager RegionsOnce your cloud credentials have been verified, you will see that the Microsoft Azure Resource Manager cloud is enabled under the Clouds tab. You will now see all of your Microsoft Azure Resource Manager resources under the Clouds menu (Clouds > AzureRM). You may need to refresh the tab to view your newly added Azure Resource Manager cloud.Adding Newly Supported RegionsAs RightScale adds support for additional ARM Regions, complete the steps below to view them in RightScale for your ARM subscriptions that have been previously registered.Complete the standard ARM registration stepsThe RightScale-Azure IntegrationRightScale uses the Azure Service Principal approach to getting permissions to operate on your subscription, which is the recommended best practice as published by Microsoft.In short, the RightScale web application is added to Azure Active Directory (AD) associated with the registered subscription. Then the RightScale application service principal (which shows up as a user) is granted the Contributor role to the subscriptions within that AD. The service principal is then used by RightScale to authenticate and make requests on your behalf. RightScale does not store any user credentials for this access in the platform. You can read more about this approach on the Microsoft Azure docs.The registration process above performs the following tasks:Adds the RightScale web application to the Azure AD (if it is not already added)Adds the RightScale application service principal (user) to the specified subscription with the Contributor roleInforms RightScale which subscription to use for this RightScale accountEach of the above steps is explained in more detail below.Add the RightScale web app to Azure ADIn order for the RightScale service principal to be granted permissions on a subscription, the RightScale web application must first be added to Azure AD. Today, there is no way to add this application directly via the Azure Portal -- note that there is a RightScale application