A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
SQL Managed Instance is the database engine only, it doesn't run the SSRS service itself, so there's no "report role" to enable on the MI side. SSRS needs its own host. The two integrate cleanly, though, and you have two paths:
Option 1 - Run SSRS against the Managed Instance
Stand up SSRS on a separate Windows VM (Azure VM or on-prem), then point it at the Managed Instance:
- The SSRS catalog databases can live on the Managed Instance - natively supported since SSRS 2019. The report server engine itself runs on the VM, not on MI.
- Connect using SQL Server authentication - MI doesn't support Windows auth, and SSRS doesn't support Entra ID (Azure AD) auth, so a stored SQL login is the only option here.
- Make sure the VM has network line-of-sight to the MI: VNet peering or a VPN gateway between the VM's VNet and the MI's VNet, with the required ports open. This is the step people most often get stuck on.
- Configure it through Report Server Configuration Manager - point the server name at your MI, choose SQL Server Account authentication, and select the ReportServer database.
Your report data sources then query the Managed Instance like any other SQL Server target.
Option 2 - Power BI Paginated Reports
If you'd rather not maintain a VM, migrate your .rdl reports to Power BI paginated reports (Premium or Fabric capacity). As mentioned by @Bruce (SqlWork.com) Migration guidance: https://learn.microsoft.com/en-us/power-bi/guidance/migrate-ssrs-reports-to-power-bi