|
| 1 | +--- |
| 2 | +title: Azure Large Instances FAQ |
| 3 | +titleSuffix: Azure Large Instances |
| 4 | +description: Provides resolutions for common issues that arise in working with Azure Large Instances for the Epic workload. |
| 5 | +ms.topic: conceptual |
| 6 | +author: jjaygbay1 |
| 7 | +ms.author: jacobjaygbay |
| 8 | +ms.custom: references_regions |
| 9 | +ms.service: azure-large-instances |
| 10 | +ms.date: 06/01/2023 |
| 11 | +--- |
| 12 | + |
| 13 | +# Frequently asked questions about the Epic workload on Azure Large Instances |
| 14 | + |
| 15 | +This article provides answers to frequently asked questions about Azure Large Instances. |
| 16 | + |
| 17 | +## In which regions is this service available? |
| 18 | + |
| 19 | +Azure Large Instances is available in the following regions: |
| 20 | + |
| 21 | +* East US |
| 22 | +* US West2 |
| 23 | +* US South Central |
| 24 | + |
| 25 | +## Do I need to give permissions to allow the deployment of a managed resource group in my subscription? |
| 26 | + |
| 27 | +No, explicit permissions aren't required but you should register the resource provider with your subscription. |
| 28 | + |
| 29 | +## Why am I not able to see the Azure Large Instances resources in Azure portal? |
| 30 | + |
| 31 | +Check Azure Policy set up if Azure Large Instances managed RGs aren't reflected in the portal. |
| 32 | +Azure subscription you use for Azure Large Instances deployments is registered with the Azure Large Instances infrastructure resource provider by the Microsoft Operations team during the provisioning process. |
| 33 | +If you don't see your deployed Azure Large Instances under your subscription, register the resource provider with your subscription. |
| 34 | +Ensure that your VNET address space provided in the request is the same as what you configure [Working with Azure large Instances in the Azure portal](work-with-azure-large-instances-in-azure-portal.md) |
| 35 | + |
| 36 | +## Is it possible to have Azure ARC installed on Azure Large Instances? |
| 37 | + |
| 38 | +It’s not mandatory, but it's possible. |
| 39 | +If you need guidance, [create a support ticket](work-with-azure-large-instances-in-azure-portal.md#open-a-support-request-for-azure-large-instances) with the Azure Customer Support team to help with your setup. |
| 40 | + |
| 41 | +## How do I monitor Azure Large Instances? |
| 42 | + |
| 43 | +Azure Large Instances is an IaaS offering and Azure teams are actively monitoring Azure Large Instances infrastructure (network devices, storage appliances, server hardware, etc.). |
| 44 | +Customer alerts related to infrastructure are provided only via Azure portal’s Service Health. |
| 45 | +Customers are highly recommended to set up Service Health alerts to get notified via their preferred communication channels when service issues, planned maintenance, or other changes happen around Azure Large Instances. |
| 46 | + |
| 47 | + For more information, see [Configure Azure Service Health Alerts](configure-azure-service-health-alerts.md) |
| 48 | + |
| 49 | +> [!NOTE] |
| 50 | +> Microsoft is not responsible for integration with any other tooling or 3P agents. |
| 51 | +Customers are responsible for any additional third-party agents that they would like to install for logging and monitoring on Azure Large Instances infrastructure. |
| 52 | + |
| 53 | +It’s also recommended to rerun Azure Large Instances GenIO test post third-party agents are installed to check for any performance variations. |
| 54 | + |
| 55 | +## How does Microsoft communicate unplanned issues? |
| 56 | + |
| 57 | +Microsoft sends service health notification only through the Azure portal. |
| 58 | +We always recommend customers to configure alerts for service health notifications. |
| 59 | + |
| 60 | +This monitoring and alerting mechanism is different than traditional mechanisms. It's recommended for customers to set up Service Health alerts to their preferred communication channels for service issues, planned maintenance, or other changes that occur around Azure Large Instances. |
| 61 | +Not setting this up could cause issues with your Azure Large Instances that might go undetected for a long time and cause downtime if not addressed at the right time. |
| 62 | + |
| 63 | +[Receive activity log alerts on Azure service notifications using Azure portal](./../service-health/alerts-activity-log-service-notifications-portal.md) |
| 64 | +## Based on my business priority, can I request a change in the “Planned” maintenance schedule for Azure Large Instances - if I must? |
| 65 | + |
| 66 | +Microsoft sends a health notification service for both planned and unplanned events. |
| 67 | +Ensure you configure health alerts for service health notifications. |
| 68 | +If due to any business dependency, you need to request a change in the planned maintenance schedule, the preferred way would be to create a service request. |
| 69 | +Planned maintenance doesn't include emergency fixes/patches required which can't be rescheduled. |
| 70 | + |
| 71 | +## Where do we create an Azure Large Instances-related Service or Support Request? |
| 72 | + |
| 73 | +You can get Help and support in the Azure portal. |
| 74 | +It's available from the Azure portal menu, the global header, or the resource menu for a service and create a Service Request. |
| 75 | +In the dropdown menu you can look for the Epic key word and then "Azure Large Instances" and select appropriate service type. |
| 76 | + |
| 77 | +## What resources are available to learn more? |
| 78 | + |
| 79 | +See [What is Azure Large Instances?](what-is-azure-large-instances.md). |
| 80 | + |
0 commit comments