RStudio Connect on Azure is perfect for proof of concepts and urgent or important shorter term projects or those with unusual compute requirements. Use push-button publishing from your RStudio IDE, scheduled execution of reports, and simple password authentication (default) to put your data products into the hands of thousands of end users or just a few colleagues in minutes and hours instead of the days or weeks that conventional enterprise provisioning or procurement can take.
RStudio Connect on Azure comes installed with 5 versions of R built from source: 3.4.4, 3.5.3, 3.6.3, 4.0.5 and 4.1.0 as well as a version of Python built from source: 3.8.9. To get started, select your compute instance, start Connect, and use your administrative privileges to adjust your configuration. You’ll be up and running in no time!
Connect to http://instance-public-ip-address:3939 and create your admin user.
To configure RStudio Connect to use a different database other than the default configuration of SQLite, see the administration guide: Changing Database Provider
To change your user authentication from the default local user account and password (e.g., integrate with your Active Directory or LDAP infrastructure), see the administration guide: Changing Authentication Provider
For all other RStudio Connect issues email email@example.com. Please note that we respond to emails during normal support hours between 9am and 5pm Monday thru Friday Eastern Time US.
The EULA is here
We do not offer refunds, however you are welcome to cancel at any time. Please be certain prior to using this Image that you are aware of the potential charges and the ways to stop charges (eg. stopping the instance or canceling the subscription).
If you believe you have found a bug in RStudio Connect itself, or you wish to give feedback on the product, please contact us at firstname.lastname@example.org and we will provide assistance over email. Note that RStudio support hours are Monday through Friday, 9am to 5pm US Eastern, so if you are having severe issues, we recommend pausing your instance to avoid incurring costs while you wait for our response.