Azure Self Supported Subscriptions

Azure is Microsoft’s cloud services environment. Today, Emory’s Azure cloud is in limited tactical use and not the primary or preferred cloud environment for use by Emory faculty and staff. Instead, faculty and staff are encouraged to use AWS at Emory cloud AWS at Emory. Nevertheless, if Azure services are required for specific departmental or project needs, then Emory’s Azure cloud is approved for limited use.  

Key Features and Benefits

Faculty or staff who need an Azure subcription should request an Azure subscription with their emory.edu email address and they also must accept the following requirements:

  • Departmental/individual use of Azure is self-supported, and departments/individuals will need to provide all technical capabilities related to setup and management of their respective Emory Azure infrastructure. If they don’t have the Azure technical capabilities needed for setup or management, faculty or staff will have to fund 3rd party technical services via an approved vendor in addition to Microsoft Azure service subscription fees. All Microsoft Azure service fees incurred by their use of Emory Azure (i.e. Azure subscriptions) are the responsibility of the department/individual.
  • All Microsoft Azure service fees incurred by their use of Emory Azure (i.e. Azure subscriptions) are the responsibility of the department/individual.
  • Faculty or staff requestors must provide a valid speed type for chargeback of the subscription costs to their department/individual funds.

  • All Azure subscriptions created will require agreement with the Emory Interim Azure Cloud Subscription Rules of Behavior by a faculty or staff member to be enabled for use. Until that process has been completed, access will be blocked from deploying infrastructure or resources in Emory’s Azure cloud. Only active faculty and staff members can request such an exception.
  • Additional subscription related costs may be added onto subscription fees in the future to support shared Emory infrastructure, connectivity, and security costs that relate to the faculty or staff’s subscription (e.g. once Emory’s network in extended into Azure, there may be additional network costs related to each subscription for example.