Deployment of Litmus Edge Manager from Azure SaaS

litmus provides litmus edge manager (lem) as a managed saas solution on azure marketplace if your organization has a custom agreement, you use a private offer for deployment a private offer is custom plan that you've negotiated with litmus that is not available on the public marketplace you deploy lem through the private offer by accepting the private offer on the azure marketplace purchasing and deploying the private on the azure marketplace activating the subscription on litmus central portal downloading and deploying litmus edge manager from litmus central portal note that private plans are offered through site model licensing this licensing model gives you full control over your infrastructure with this model you deploy the infrastructure but no license is included you request a license separately from the litmus account team tag consumption is not monitored or billed you maintain full control over your virtual machines litmus has no access to your environment prerequisites before you being, ensure that you have negotiated a private plan with litmus access to https //portal azure com/ step 1 accept the private offer log in to https //portal azure com/#home and search for marketplace in the left navigation menu, select private offer management in the private offer management page, click view + accept for the litmus edge manager saas site model offer next, a page displays with offer details and terms and conditions review this information, confirm that you've read the terms and conditions, and click accept private offer then you're returned to the private offer management page step 2 purchase and deploy the private offer in the private offer management page, click purchase for the litmus edge manager saas site model offer in the right pane, define the following settings resource group select a resource group in which to place the saas instance name provide a name for the litmus edge manager saas offering that you're subscribing to billing term select a 1, 2, or 3 year subscription recurring billing decide on whether to automatically renew after the subscription expires click review + subscribe , review subscription settings again if necessary and click subscribe the subscription progress page displays while the saas subscription is setting up when complete, the offering has been deployed once complete, click configure account now and you are directly to the azure marketplace activation page in https //portal litmus io/ the link redirects you to the azure marketplace activation page in central portal step 3 activate the subscription in litmus central portal on the azure marketplace activation page in central portal, click activate subscription a message displays indicating that microsoft is finalizing the activation when complete, click deploy to azure you also receive an email from microsoft confirming that the saas subscription is active step 4 deploying to azure in the custom deployment page in azure, specify template settings for the deployment required parameters true 175,765left unhandled content type left unhandled content type left unhandled content type left unhandled content type vm configuration true 188,448 40031897926633,303 59968102073367left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type network configuration true 279,329 9728867623605,331 0271132376395left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type public ip configuration true 284,327 4768740031898,328 5231259968102left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type unhandled content type tags enter tags in the parameter field as json using the following syntax {"environment" "production", "costcenter" "it 12345", "owner" "admin\@company com"} true 295,645left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type step 5 accessing litmus edge manager after deployment completes, you can access the lem administration console at https //\<public ip> 8446 access the web interface at https //\<public ip> ssh to the vm using ssh \<adminusername>@\<public ip> note that port 22 (ssh) is blocked by the firewall by default create an inbound rule that allows tcp traffic on port 22 before you connect