Security at a glance: SSRS Reports Migration Wizard runs locally on the customer’s Windows machine. Internet communication is used for license activation; offline activation is available when internet access is not permitted.
Last updated: November 14, 2026
Security Model #
- Runs locally: The wizard is installed and executed on the customer’s Windows machine.
- Local processing: Migration content is processed within the customer’s environment and is not uploaded to AzureOps as part of standard migration.
- No telemetry: The wizard does not collect or transmit product-usage telemetry to AzureOps. Internet communication is used for license activation only.
Licensing and Internet Connectivity #
- Online activation contacts the AzureOps licensing server once to activate the license.
- This licensing communication is separate from report-server migration.
- If the migration machine cannot access the internet, customers can use the offline activation process on demand.
Credentials and Data Protection #
- Source and target connection profiles are distinguished by report-server URL and username. Selecting a profile restores its authentication choice and username.
- Remembered connection passwords are protected with Windows Data Protection API (DPAPI) for the current Windows user.
- This protection applies to remembered connection-profile passwords only; it does not imply the same protection for credentials in SRMW files or every other secret.
- Protect the migration workstation and ensure only authorized users can access credentials.
- For file-share subscription credentials and source-password limitations, see Getting Started.
Data in Transit #
- Report-server migration traffic: The wizard communicates with the configured SSRS or Power BI Report Server through its SSRS SOAP endpoint. When the endpoint is configured with HTTPS, report-server communication, including authentication information and migration requests, is protected in transit by TLS.
- HTTP endpoints: HTTP does not provide transport encryption. Customers should use HTTPS for report-server endpoints whenever supported by their environment and security policy.
Optional SRMW File Migration #
SRMW files provide an export and import mechanism for migration information when a direct connection between source and target report servers is not possible. They are not required for a standard server-to-server migration.
- If data-source credentials are updated before export, the generated
.srmwfile may contain those credentials in plain text. Treat the file as sensitive: store it securely, transfer it only through an approved channel, and delete temporary copies when they are no longer needed.
Diagnostics and Support #
- The wizard does not automatically upload migration content or migration logs to AzureOps as part of the normal migration workflow.
- If support requires logs or diagnostic files, customers should share only information approved by their internal security policy.
Exported Results and Diagnostic Logs #
The wizard can export filtered CSV migration-result details and display full per-item diagnostic messages and chronological migration logs. These exports and diagnostics may contain sensitive operational information, including catalog paths, source and target report-server names, usernames, connection strings, operation details, SOAP traces, error messages, exception traces, and diagnostic timestamps.
- Store exported result details and logs only in locations approved by your organization.
- Follow customer policies for retention, secure transfer, and deletion of exported files and logs.
- Review information before sharing it externally. Redact passwords, connection-string secrets, access tokens, sensitive usernames, and other confidential values.
- Share only the diagnostic excerpts required for support unless the support team specifically requests additional information and your policy permits it.
The wizard does not automatically upload report content, exported result details, or migration logs to AzureOps as part of the normal migration workflow. Customers control how exported results and diagnostic information are stored and shared.
Customer Security Responsibilities #
- Use accounts with only the permissions required for the selected migration tasks.
- Use authorized accounts to access the source and target report servers and the machine running the wizard.
- Use HTTPS where it is configured and appropriate for the report-server environment.
- Follow organizational policies for passwords, secrets, backups, exported files, and log retention.
- Review migrated permissions, data-source settings, subscriptions, and schedules before enabling production workloads.
Compliance Considerations #
The wizard’s local execution can help organizations design migration procedures that align with internal data-residency and change-management requirements. However, using the wizard does not by itself constitute certification or compliance with a particular regulation, framework, or customer policy.
Customers are responsible for assessing the complete migration process against their applicable requirements, including workstation security, report-server permissions, credential handling, file storage, retention, licensing, and support-log sharing.
Need More Information? #
For setup and access requirements, see the Prerequisites page. For the migration workflow, see Getting Started.