Back to Azure Resource templates index <–
SignalR Service
Template Locations
Infrastructure As Code Advisor (Beta)
WAF-compliance
The WAF-compliance advisor validates templates based on the Well Architected Framework practices. Every day a GitHub Action updates the templates compliance data and lists the recomendations.
Sustainbility Advisor
The sustainability advisor is based on the Sogeti Cloud Reference Architecture with sustainble practices. These sustainble practices cover application code, cloud infrastructures and data. The global Sogeti community is continously evolving the sustainble practices and every day new and tuned are added. For cloud infrastructures the sustainble practices are automatically validated and reported below.
note: when 100% it can be that there is no sustainble practices yet for this Cloud infrastructure.
Online documentation
Template reference
Service description
Requirements
- Resource group must been created with a valid name and location.
Input values
- tagBillingIdentifier : BillingIdentifier tag.
- SignalRSkuName : SignalR Service Sku.
- signalRTier : SignalR Service Tier
- signalRCapacity : Number of instances for the SignalR Service
Output values
- SignalRName
- SignalRAccessKey
- SignalRConnectionString
Compliance Advisor details
Resource Health Result
| Message | ResourceType | Severity |
|---|---|---|
| Location for the resource should not be hardcoded, it should be parameterized and should refer from Resource Group's location i.e. [resourceGroup().location] | Microsoft.SignalRService/SignalR | 2 |
| Your current API Version i.e.2018-10-01 for the resource Microsoft.SignalRService/SignalR is outdatedconsider updating to new recent version available i.e. 2023-03-01-preview or 2023-02-01 | Microsoft.SignalRService/SignalR | 2 |
| To help other contributors understand the purpose of the resource, specify comments for each resource in the template | Microsoft.SignalRService/SignalR | 1 |
TemplateParameterHealthResult
| Message | Severity |
|---|---|
| It is recommended to make your parameter as camel case, wherever possible for i.e. tagsRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. signalrCustomnameRead More | 1 |
TemplateVariableHealthResult
| Message | Severity |
|---|---|
| It is recommended to make your variable as camel case, wherever possible for e.g. environmentRead More | 1 |
| It is recommended to make your variable as camel case, wherever possible for e.g. locationRead More | 1 |