Quality checks for Azure Large Instances
This article provides an overview of Azure Large Instances for Epic® quality checks.
The Microsoft operations team performs a series of extensive quality checks to ensure that customers' requests to run Azure Large Instances for Epic are fulfilled accurately, and that infrastructure is healthy before handover. However, customers are advised to perform their own checks to ensure services have been provided as requested, including the following:
- Basic connectivity
- Latency check
- Server health check from operating system
- OS level sanity checks / configuration checks
The following sections identify quality checks often performed by Microsoft teams before the infrastructure handover to the customer.
Network
- IP blade information
- Access control list on firewall
Compute
- Number of processors and cores for servers
- Accuracy of memory size for the assigned server
- Latest firmware version on the blades
Storage
- Size of boot LUN and FC LUNs are consistent with the Azure Large Instances on Epic standard configuration
- SAN configuration
- Required VLANs creation
Operating System
- Accuracy of LUNs
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for