Reporting Hub Knowledge Center
  • Reporting Hub Knowledge Center
  • GETTING STARTED
    • Required Azure Services
    • Deployment Step-by-Step
      • Self-Serve Guided Install
      • Enable Power BI Service Settings
      • Configure Reporting Hub App Settings
      • Set Your Home Page
    • Azure Marketplace Install
  • CONCEPTS
    • Reporting Hub Architecture
    • AaaS end-to-end Architecture
    • Security & Trust Center
  • TUTORIALS
    • Azure Portal Administration
    • App Settings
      • Tenant Admin
        • Tenant Switching
      • Managing Your Subscription
      • Authentication Admin
      • Language Admin
      • SMTP Setup
      • Payment Provider Integrations
      • Notifications Admin
    • Embedded Capacity Admin
      • Switching to a Fabric Capacity
    • Connect Power BI Workspaces
    • Customize Theme
      • Branding (Images and Text)
      • Theme and Layout
      • Colors
        • Colors Overview
      • Fonts
    • Managing Content
      • The Manage Navigation Menu
      • Adding a Category
      • Embedding Power BI Content
      • Row Level Security
      • Search Tags
      • Content Page Options
      • Embedding a URL Page
      • Create Embed URL Links
    • Report Options
      • Create Report Bookmarks
      • Schedule Email Reports
      • Favorites
    • Managing Your Gateway
    • User Management
      • Managing User Access
      • Managing Groups
      • Managing Users in Entra ID
    • Secondary Environment (Test/Prod)
    • Embed the Reporting Hub in Your App
    • Usage Analytics
      • App Usage Tracking with Google Analytics
      • App Usage Tracking with SQL DB
    • App Performance
    • Azure Resource Monitoring
    • Self-Serve Guided Updates
  • Reference
    • What's new in the Reporting Hub?
    • Troubleshooting
    • Support Runbooks
      • Critical System Outage (L1)
      • Users Unable to Access (L2)
      • Content Not Available (L2)
      • Application is slow/getting slower (L2)
      • Capacity not starting/stopping automatically
Powered by GitBook
On this page
  1. Reference

Support Runbooks

There are steps you can take to help resolve issues you may be facing.

PreviousTroubleshootingNextCritical System Outage (L1)

Last updated 11 months ago

Please take a look at our page for solutions before creating a support ticket.

For example, Lock outs are common due to the wrong authentication being selected or you've created a sub-tenant and now you're stuck in the sub-tenant. These are not Level 1 or 2 outages and can be resolved quickly on your own by following the guidance provided.

Definition of each severity level of issue so we can walk you through the correct steps to resolve.

​

This level is reserved for issues that result in a complete system outage, making it impossible for anyone to access the service. This could be caused by a major bug, a hardware failure, or other critical Azure services issue that requires immediate attention.​

This level is for issues that cause a significant degradation of service, but do not result in a complete outage. This could include things like slow response times, errors preventing certain actions, or issues affecting a subset of users. While the service may still be usable, the issue is significant enough to warrant attention.

​Level 3 – Minor impact/Most of the system is functioning properly.​

This level is for issues that are causing only minor disruptions to the service. Most of the system is still functioning as expected, but there may be some small issues affecting a small subset of users. While not urgent, these issues should still be addressed to ensure a smooth user experience.

​Level 4 – Low Impact/Informational request

Th​is level is for minor issues or questions that do not significantly impact the service. This could include things like cosmetic issues, minor functionality questions, or feature requests. While not a priority, it's still important to address these concerns to provide the best possible service.

For anything not covered within our documentation please contact our support team at:

Common Troubleshooting
​Level 1 – Critical Impact/System Down. Complete system outage.
Level 2 – Significant Impact/Severe downgrade of services. Specific users/group outage.​
SupportReporting Hub Support
Logo