Answers to questions about Azure that we often see at Cornell |
To request a Cornell Azure subscription, or to migrate an Azure subscription you already have to the Cornell Azure Enterprise Agreement, complete this form: https://cornell.qualtrics.com/jfe/form/SV_5nWBzF2mrsHRAwJ
Login to https://portal.azure.com with your Cornell netId credentials. If the login process asks you, choose "school/work account", not "microsoft.com account".
Azure support is free at present, whether you seek it directly from Azure or ask the CIT Cloud Team.
You can request support from Azure directly or from the CIT Cloud Team.
Billing for Azure is handled through CloudCheckr. Invoices are sent out monthly.
The list cost for each service at Azure can be seen here : https://azure.microsoft.com/en-us/pricing/calculator/
Cornell does receive a discount by virtue of having an Enterprise Agreement (EA) with Microsoft. Any subscription that is under our EA automatically receives the discount. To see the exact EA price for each Azure resource, please follow the instructions here : Azure Pricing Calculator
Yes there is a data egress waiver. See https://azure.microsoft.com/en-us/blog/azure-egress-fee-waiver-for-the-academic-community/
The egress waiver is automatic. There is nothing that the customer has to do to receive the benefit.
Yes. Campus 10 space has been extended to Azure via an ExpressRoute connection.
Yes! You can use any combination of individual netIDs and/or security groups to meet your need. Documentation to make permission changes is available directly from Microsoft.
You can as long as they have a Microsoft account. Any person from an institution that is using O365 will have a Microsoft account. Additionally, even personal Microsoft accounts can be invited. You can scope their access as appropriate from the subscription as a whole even down to the individual resource level.
Microsoft offers a free online learning path for Azure Fundamentals. In addition to that, within the Microsoft Learn training options, there are currently 1,381 related to "Azure".
Additional training opportunities are available here: Azure Training
Images from the Azure Marketplace should include default configurations for system clock management. These range from using an emulated real-time-clock within the guest or reaching out to public network time servers around the world.
In cases where you have configured restrictive Network Security Groups (NSG) that limit out-bound traffic, you should confirm that outbound probes to NTP servers are permitted. Typically, this traffic operates on UDP port 123. No special in-bound rules are required, since NSGs at Azure are stateful.
Additional details may be found in Microsoft's published guidelines for clock synchronization when running Linux platforms or Windows platforms in Azure.
The MAC does not change until you delete the network interface. Here’s the official documentation answer : https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-faq#will-the-mac-address-remain-the-same-for-my-vm-once-its-created
Azure VMs can exist in several states including “stopped” and “stopped (deallocated)”. Shutting down the VM from within the OS puts the VM in a “stopped” state. In that state you still accrue charges for the VM and for any OS and data disks. Putting the VM in a “deallocated” state releases the hold on the backend Azure host resources so once the VM is in that state you are not charged for the VM but you are still charged for the OS and any data disks. Here is some more information : https://blogs.technet.microsoft.com/uspartner_ts2team/2014/10/10/azure-virtual-machines-stopping-versus-stopping-deallocating/
All Windows Server images at Azure are provisioned by default with a 128GB OS disk. Azure does not officially support shrinking the size of the OS disk. To provision a Windows Server with a smaller (32GB) OS disk, you need to select the OS image that is indicated as "smalldisk". Growing the OS disk can be done at any time after the VM is in a "deallocated" state. See how to grow a disk at Azure.
The Azure cloud provides its own DNS service, which is perfect for virtual machines that do not need to look up 10-space addresses in Cornell's DNS. If you have applications or servers that require the ability to turn a Cornell "10.x.y.z" IP address into a host name, you will need to replace Azure's DNS servers with ones run by Cornell. See DNS Resolution for Azure Virtual Machines for more information.
https://microsoft.github.io/AzureTipsAndTricks/
https://docs.microsoft.com/en-us/azure/migrate/contoso-migration-overview
https://confluence.cornell.edu/x/GDeJFg