chrishuffman5/analytics-ssrs-2025
skills/analytics/ssrs/2025/SKILL.md
Version-specific expert for SQL Server 2025 reporting, where SSRS is replaced by Power BI Report Server (PBIRS). Covers migration guidance, licensing changes, and the SSRS-to-PBIRS transition. WHEN: "SSRS 2025", "SQL Server 2025 reporting", "SSRS replacement", "SSRS end of life", "SSRS to PBIRS", "SSRS migration to Power BI Report Server".
$ install --global
skillsauthnpx skillsauth add chrishuffman5/domain-expert analytics-ssrs-2025Install this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 26, 2026, 4:31 AM23.8s1 file scanned
SKILL.md
- name:
- analytics-ssrs-2025
- description:
- Version-specific expert for SQL Server 2025 reporting, where SSRS is replaced by Power BI Report Server (PBIRS). Covers migration guidance, licensing changes, and the SSRS-to-PBIRS transition. WHEN: \"SSRS 2025\", \"SQL Server 2025 reporting\", \"SSRS replacement\", \"SSRS end of life\", \"SSRS to PBIRS\", \"SSRS migration to Power BI Report Server\".
- license:
- MIT
- version:
- 1.0.0
- author:
- christopher huffman
SQL Server 2025 Reporting — SSRS Replaced by PBIRS
You are a specialist in the reporting transition for SQL Server 2025. There is no SSRS version for SQL Server 2025. Microsoft has consolidated all on-premises reporting under Power BI Report Server (PBIRS).
For foundational SSRS knowledge, refer to the parent technology agent. This agent focuses on the strategic shift, licensing changes, and migration guidance.
The Strategic Shift
- SSRS 2022 is the last standalone SSRS release
- Power BI Report Server is the default on-premises reporting solution for SQL Server 2025
- SSRS 2022 continues receiving security patches through January 2033
- No new SSRS features will be developed
Licensing Changes
| Aspect | Before SQL Server 2025 | SQL Server 2025 | |--------|----------------------|-----------------| | PBIRS access | Enterprise Edition with Software Assurance only | Any paid SQL Server edition | | SSRS access | Included with SQL Server license | No new version; use SSRS 2022 or migrate | | Impact | PBIRS was premium-only | PBIRS now broadly available |
This is a significant licensing democratization. Standard Edition customers can now use Power BI Report Server.
Migration Paths
Path 1: SSRS to PBIRS (On-Premises) — Low to Medium Complexity
PBIRS is backward-compatible with SSRS RDL reports. Migration steps:
- Install Power BI Report Server
- Back up SSRS encryption key and ReportServer database
- Restore/attach ReportServer database to PBIRS instance
- Restore encryption key
- Verify report rendering and data source connections
- Update client bookmarks and application integrations
Most reports work without modification. Shared data sources, datasets, subscriptions, and schedules are preserved.
Path 2: SSRS to Power BI Service (Cloud) — Medium to High Complexity
For organizations moving to cloud-based reporting:
- RDL Migration Tool (
microsoft/RdlMigrationon GitHub) automates conversion and publishing of RDL reports to Power BI Service workspaces - Shared datasets/data sources must be converted to embedded (the tool handles this)
- Power BI gateway required for on-premises data sources
- Custom code assemblies in RDL are not supported in Power BI Service (key migration blocker)
- Requires Power BI Premium, Premium Per User, or Fabric capacity
Path 3: Rebuild as Power BI Interactive Reports — High Complexity
Complete redesign from paginated (RDL) to interactive (PBIX) reports. Different paradigm -- only appropriate for dashboards and ad-hoc analysis. Paginated operational reports should remain as RDL.
When to Choose Each Path
| Scenario | Recommendation | |----------|---------------| | New deployments | Power BI Report Server | | Existing SSRS, no migration budget | Continue SSRS 2022 (supported until 2033) | | Need interactive dashboards on-premises | Power BI Report Server | | Need only paginated/operational reports | Either works; PBIRS preferred for future-proofing | | SQL Server 2025 license | Power BI Report Server (included) | | Moving to cloud | Power BI Service with RDL Migration Tool |
PBIRS Feature Additions Over SSRS
- Host interactive Power BI reports (.pbix) on-premises
- Power BI data models (DAX, DirectQuery)
- Scheduled data refresh for Power BI reports
- More frequent update cadence (roughly every 4 months)
- Row-level security via Power BI RLS (in addition to query-based filtering)
Support Timeline
| Version | Extended Support Ends | |---------|----------------------| | SSRS 2016 | July 2026 | | SSRS 2017 | October 2027 | | SSRS 2019 | January 2030 | | SSRS 2022 | January 2033 | | PBIRS | Updated quarterly, aligned with SQL Server |
Related Skills
chrishuffman5/kubectl
tools
VerifiedTrustedCommunity
kubectl command-line usage and scripting: kubeconfig and context management, output formats (jsonpath, custom-columns, go-template), all major verbs (get, describe, apply, delete, exec, logs, port-forward, rollout, scale, drain), workload resources, config/storage, networking, RBAC, node management, debugging (CrashLoopBackOff, ImagePullBackOff, OOMKilled), and scripting patterns (dry-run, diff, wait, jq, kustomize). WHEN: "kubectl", "k8s CLI", "kubeconfig", "namespace", "pod", "deployment", "service", "ingress", "configmap", "secret", "rollout", "scale", "drain", "taint", "kustomize". Do NOT use for cluster architecture, sizing, upgrades, or workload design decisions — that's the `kubernetes` skill in the `containers` plugin. This skill is command syntax and scripting kubectl against an existing cluster, not cluster ops.
3SKILL.mdUpdated Jul 21, 2026
chrishuffman5/bash
tools
VerifiedTrustedCommunity
Bash 5.x shell scripting, Unix text processing, and command-line automation: variables, parameter expansion, quoting, control flow, functions, I/O redirection, error handling (set -euo pipefail, trap), and the Unix tool ecosystem (grep, sed, awk, jq, find, sort, uniq, cut, xargs). Covers process management, networking (curl, ssh, rsync, nc), file locking (flock), parallel execution, and production script patterns. WHEN: "Bash", "bash", "shell", "sh", ".sh", "shell script", "sed", "awk", "grep", "jq", "find", "xargs", "curl", "ssh", "rsync", "cron", "pipe", "redirect", "here-doc", "shebang", "POSIX", "set -euo pipefail", "trap".
3SKILL.mdUpdated Jul 21, 2026
chrishuffman5/azure-cli
tools
VerifiedTrustedCommunity
Azure CLI (az) command syntax and scripting: authentication (interactive, service principal, managed identity, SSO), output formats and JMESPath queries, resource groups, VMs, storage accounts/blobs, networking (VNets, NSGs, load balancers, DNS), Entra ID, AKS, App Service, Functions, databases (SQL, Cosmos DB, MySQL, PostgreSQL), Key Vault, Monitor/alerting, and infrastructure scripting patterns. WHEN: "az ", "Azure CLI", "az login", "az vm", "az aks", "az storage", "az keyvault", "az monitor", "az ad", "az group", "az network", "az webapp", "az functionapp", "az sql", "az cosmosdb", "JMESPath", "az account". Do NOT use for Azure architecture, landing zones, or multi-subscription strategy — that's the `cloud-platforms` plugin. This skill is about command syntax and scripting the CLI, not deciding what to provision.
3SKILL.mdUpdated Jul 21, 2026
chrishuffman5/aws-cli
tools
VerifiedTrustedCommunity
AWS CLI v2 command syntax and scripting: authentication (profiles, SSO, assume-role, instance profiles), output formats and JMESPath queries, pagination and waiters, IAM, S3, Lambda, RDS, CloudFormation, ECS, EKS, CloudWatch, SSM, Route 53, STS, and VPC networking. WHEN: "aws ", "AWS CLI", "aws ec2", "aws s3", "aws lambda", "aws iam", "aws cloudformation", "aws ssm", "aws ecs", "aws eks", "aws rds", "aws cloudwatch", "aws route53", "aws sts". Do NOT use for AWS architecture, service selection, multi-account strategy, or FinOps — that's the `cloud-platforms` plugin. This skill is about command syntax and scripting the CLI, not deciding what to provision.
3SKILL.mdUpdated Jul 21, 2026