Connecting Service Provider Console to Pulse
The tutorial begins with the foundational step of connecting the Veeam Service Provider Console to Pulse, Veeam's online portal for license management and usage reporting. The process requires generating a one-year authentication token from the Pro Partner portal and entering it into the console's Pulse plugin configuration. Once connected, administrators enable two critical features: company management (which maps Service Provider Console companies to Pulse companies) and license key management (which allows license creation and distribution through the console). The company mapping functionality supports auto-mapping, manual mapping, and merging capabilities, enabling service providers to align their customer hierarchies across both systems. This integration is particularly valuable for managing multi-site customers where a single Pulse company entry can be mapped to multiple Service Provider Console companies representing different locations.
License Key Creation and Distribution
The console streamlines license key management by allowing administrators to create product-specific licenses directly within the interface. When creating a license for Veeam Backup & Replication, administrators select the edition (such as Enterprise Plus), specify workload types (VMs, agents, file shares, public cloud), and define quantities for each workload category. After creation, licenses must be assigned to a Pulse company before they can be deployed. The console then enables direct license installation to Veeam servers without manual file transfers—administrators simply navigate to the target server in the licensing tab and select 'Install from Pulse' to push the license remotely. This capability eliminates the traditional workflow of downloading license files, placing them on file shares, and manually installing them on each Veeam server, significantly reducing administrative overhead for service providers managing multiple customer environments.
Multi-Tenant Licensing Strategies
Veeam's licensing approach varies significantly based on deployment architecture. For dedicated Veeam Backup & Replication servers, the current best practice requires creating individual license keys for each customer—a shift from the legacy approach of using one large key across all servers. This per-customer licensing is mandatory for auto-reporting functionality. However, multi-tenant scenarios follow different rules: when a single Veeam Backup for Microsoft 365 server protects multiple customers, administrators create one consolidated license covering all users across all tenants and assign it to their own company (the service provider) rather than to individual customers. Similarly, for Veeam Agents managed directly by the Service Provider Console (not by customer Veeam servers), a master agent license is created covering all server and workstation agents across all customers, assigned to the service provider company, and installed directly on the console itself. This master key approach for multi-tenant scenarios enables auto-reporting and eliminates the need to update individual agent licenses upon expiration.
Usage Reporting and Auto-Reporting Configuration
The Service Provider Console provides comprehensive usage reporting that breaks down consumption by product type (Backup & Replication editions, agents, Microsoft 365, public cloud workloads) and by customer. While administrators can manually review these reports and submit usage to Pulse monthly, Veeam offers two automation options: auto-populate/auto-submit and auto-reporting. Auto-populate/auto-submit bills based on licenses cut rather than actual usage, which can lead to overcharges if licenses are created accidentally or if customer workloads fluctuate. Auto-reporting, the recommended approach, automatically captures actual consumption data and submits it to Pulse for review before final submission to the aggregator. Enrolling in auto-reporting requires accurate license key allocation (individual keys per customer server, no shared keys across multiple servers) and enabling automatic report approval in the console. With automatic report approval enabled, usage data is force-collected on the first of each month rather than waiting for manual review on each Veeam server, ensuring timely reporting and eliminating the delays that occur when administrators don't manually approve usage reports by the 10th of the month.
