Support

For issues with MCA Continuity, contact:

Email: support@savoysystems.ai

Scope of Support

Savoy

Application issues — data collection, Power BI connectivity, dashboard, configuration

Microsoft

Azure infrastructure issues — Function App availability, SQL Database connectivity, network

Microsoft

Billing and subscription issues — Marketplace charges, free trial

Deployment Prerequisites

Most enterprise subscriptions meet these by default — but restricted, MSDN, free-tier, or newly created subscriptions may not.

Resource provider registration

The application requires the microsoft.operationalinsights resource provider, which is not registered by default on new subscriptions. To check and register:

# Check registration status
az provider show -n microsoft.operationalinsights --query registrationState -o tsv

# Register if it shows "NotRegistered"
az provider register -n microsoft.operationalinsights

Registration typically completes within 1–2 minutes. You can also register in the Azure Portal: Subscription → Resource providers → search "operationalinsights" → Register.

Regional quota for App Service

The Function App runs on a B1 Basic App Service plan. Some subscriptions have zero quota in certain regions. If deployment fails with "Operation cannot be completed without additional quota," either:

  • Choose a different region. The application supports any region with Azure Functions, Storage, and SQL Database.
  • Request a quota increase. In the Azure Portal: Subscription → Usage + quotas → Request increase → search for "App Service" → select the B1 SKU in your desired region.
Azure SQL availability in your region

Some subscriptions restrict SQL Database provisioning in certain regions. If deployment fails with "Provisioning is restricted in this region," redeploy in a different region. West US 2, West Europe, and North Europe tend to have the broadest availability.

Common Issues

Subscriptions showing "Permission Denied"

The application's service principal does not have Cost Management Reader access to the subscription. This is typically inherited from the root management group role assignment. To fix:

  1. Open the Subscriptions & Health tab in the application dashboard
  2. Find the affected subscription
  3. Run the PowerShell command shown in the remediation guidance, or re-run the onboarding script
No data appearing after deployment

Data collection runs on a schedule (default: daily at 2 AM UTC). To trigger an immediate collection:

  1. Open the application in the Azure portal
  2. Click "Trigger Data Collection" on the Overview tab
  3. Allow 30–60 minutes for the initial collection to complete

For the first run, the application collects up to 13 months of historical data, which may take 2–3 hours for large tenants.

Power BI can't connect to the SQL database

The SQL Database firewall must allow your IP address. In the Azure portal:

  1. Navigate to the SQL Server resource in the managed resource group
  2. Go to Networking → Firewall rules
  3. Add your client IP address or enable "Allow Azure services and resources to access this server"

For Power BI Service (cloud), ensure "Allow Azure services" is enabled.