⚶ Changes
{
"#id": "SignalR_CreateOrUpdate",
"$parameters": {
"parameters": {
"Description": {
"new": "A class representing a resource.",
"old": "A class represent a resource."
},
"$properties": {
"properties": [
{
"#name": "features",
"Description": {
"new": "List of the featureFlags.\n\nFeatureFlags that are not included in the parameters for the update operation will not be modified.\nAnd the response will only include featureFlags that are explicitly set.\nWhen a featureFlag is not explicitly set, its globally default value will be used\nBut keep in mind, the default value doesn't mean \"false\". It varies in terms of different FeatureFlags.",
"old": "List of the featureFlags.\r\n\r\nFeatureFlags that are not included in the parameters for the update operation will not be modified.\r\nAnd the response will only include featureFlags that are explicitly set. \r\nWhen a featureFlag is not explicitly set, its globally default value will be used\r\nBut keep in mind, the default value doesn't mean \"false\". It varies in terms of different FeatureFlags."
},
"$items": {
"$properties": [
{
"#name": "flag",
"Description": {
"new": "FeatureFlags is the supported features of Azure SignalR service.\n- ServiceMode: Flag for backend server for SignalR service. Values allowed: \"Default\": have your own backend server; \"Serverless\": your application doesn't have a backend server; \"Classic\": for backward compatibility. Support both Default and Serverless mode but not recommended; \"PredefinedOnly\": for future use.\n- EnableConnectivityLogs: \"true\"/\"false\", to enable/disable the connectivity log category respectively.\n- EnableMessagingLogs: \"true\"/\"false\", to enable/disable the connectivity log category respectively.\n- EnableLiveTrace: Live Trace allows you to know what's happening inside Azure SignalR service, it will give you live traces in real time, it will be helpful when you developing your own Azure SignalR based web application or self-troubleshooting some issues. Please note that live traces are counted as outbound messages that will be charged. Values allowed: \"true\"/\"false\", to enable/disable live trace feature.",
"old": "FeatureFlags is the supported features of Azure SignalR service.\r\n- ServiceMode: Flag for backend server for SignalR service. Values allowed: \"Default\": have your own backend server; \"Serverless\": your application doesn't have a backend server; \"Classic\": for backward compatibility. Support both Default and Serverless mode but not recommended; \"PredefinedOnly\": for future use.\r\n- EnableConnectivityLogs: \"true\"/\"false\", to enable/disable the connectivity log category respectively.\r\n- EnableMessagingLogs: \"true\"/\"false\", to enable/disable the connectivity log category respectively.\r\n- EnableLiveTrace: Live Trace allows you to know what's happening inside Azure SignalR service, it will give you live traces in real time, it will be helpful when you developing your own Azure SignalR based web application or self-troubleshooting some issues. Please note that live traces are counted as outbound messages that will be charged. Values allowed: \"true\"/\"false\", to enable/disable live trace feature."
}
}
]
}
},
{
"liveTraceConfiguration": [
{
"#name": "enabled",
"Description": {
"new": "Indicates whether or not enable live trace.\nWhen it's set to true, live trace client can connect to the service.\nOtherwise, live trace client can't connect to the service, so that you are unable to receive any log, no matter what you configure in \"categories\".\nAvailable values: true, false.\nCase insensitive.",
"old": "Indicates whether or not enable live trace.\r\nWhen it's set to true, live trace client can connect to the service.\r\nOtherwise, live trace client can't connect to the service, so that you are unable to receive any log, no matter what you configure in \"categories\".\r\nAvailable values: true, false.\r\nCase insensitive."
}
},
{
"categories": {
"$properties": [
{
"#name": "name",
"Description": {
"new": "Gets or sets the live trace category's name.\nAvailable values: ConnectivityLogs, MessagingLogs.\nCase insensitive.",
"old": "Gets or sets the live trace category's name.\r\nAvailable values: ConnectivityLogs, MessagingLogs.\r\nCase insensitive."
}
},
{
"#name": "enabled",
"Description": {
"new": "Indicates whether or the live trace category is enabled.\nAvailable values: true, false.\nCase insensitive.",
"old": "Indicates whether or the live trace category is enabled.\r\nAvailable values: true, false.\r\nCase insensitive."
}
}
]
}
}
]
},
{
"resourceLogConfiguration": [
{
"categories": {
"$properties": [
{
"#name": "name",
"Description": {
"new": "Gets or sets the resource log category's name.\nAvailable values: ConnectivityLogs, MessagingLogs.\nCase insensitive.",
"old": "Gets or sets the resource log category's name.\r\nAvailable values: ConnectivityLogs, MessagingLogs.\r\nCase insensitive."
}
},
{
"#name": "enabled",
"Description": {
"new": "Indicates whether or the resource log category is enabled.\nAvailable values: true, false.\nCase insensitive.",
"old": "Indicates whether or the resource log category is enabled.\r\nAvailable values: true, false.\r\nCase insensitive."
}
}
]
}
}
]
},
{
"serverless": [
{
"#name": "connectionTimeoutInSeconds",
"Description": {
"new": "Gets or sets Client Connection Timeout. Optional to be set.\nValue in seconds.\nDefault value is 30 seconds.\nCustomer should set the timeout to a shorter period if messages are expected to be sent in shorter intervals,\nand want the client to disconnect more quickly after the last message is sent.\nYou can set the timeout to a longer period if messages are expected to be sent in longer intervals,\nand they want to keep the same client connection alive during this session.\nThe service considers the client disconnected if it hasn't received a message (including keep-alive) in this interval.",
"old": "Gets or sets Client Connection Timeout. Optional to be set.\r\nValue in seconds.\r\nDefault value is 30 seconds.\r\nCustomer should set the timeout to a shorter period if messages are expected to be sent in shorter intervals,\r\nand want the client to disconnect more quickly after the last message is sent.\r\nYou can set the timeout to a longer period if messages are expected to be sent in longer intervals,\r\nand they want to keep the same client connection alive during this session.\r\nThe service considers the client disconnected if it hasn't received a message (including keep-alive) in this interval."
}
},
{
"#name": "keepAliveIntervalInSeconds",
"Description": {
"new": "Gets or sets the Keep-Alive Interval. Optional to set.\nValue is in seconds.\nThe default value is 15 seconds.\nCustomers should set this value to a shorter period if they want the service to send keep-alive messages more frequently,\nensuring timely checks of the connection status.\nConversely, customers can set this value to a longer period if they want the service to send keep-alive messages less frequently,\nreducing network traffic, but note that it may take longer to detect a disconnection.\nThis interval ensures that the connection is maintained by sending periodic keep-alive messages to the client.",
"old": "Gets or sets the Keep-Alive Interval. Optional to set.\r\nValue is in seconds.\r\nThe default value is 15 seconds.\r\nCustomers should set this value to a shorter period if they want the service to send keep-alive messages more frequently, \r\nensuring timely checks of the connection status.\r\nConversely, customers can set this value to a longer period if they want the service to send keep-alive messages less frequently, \r\nreducing network traffic, but note that it may take longer to detect a disconnection.\r\nThis interval ensures that the connection is maintained by sending periodic keep-alive messages to the client."
}
}
]
},
{
"upstream": [
{
"templates": {
"Description": {
"new": "Upstream template item settings. It defines the Upstream URL of the incoming requests.\nThe template defines the pattern of the event, the hub or the category of the incoming request that matches current URL template.",
"old": "Upstream template item settings. It defines the Upstream URL of the incoming requests.\r\nThe template defines the pattern of the event, the hub or the category of the incoming request that matches current URL template."
},
"$properties": [
{
"#name": "hubPattern",
"Description": {
"new": "Gets or sets the matching pattern for hub names. If not set, it matches any hub.\nThere are 3 kind of patterns supported:\n1. \"*\", it to matches any hub name.\n2. Combine multiple hubs with \",\", for example \"hub1,hub2\", it matches \"hub1\" and \"hub2\".\n3. The single hub name, for example, \"hub1\", it matches \"hub1\".",
"old": "Gets or sets the matching pattern for hub names. If not set, it matches any hub.\r\nThere are 3 kind of patterns supported:\r\n 1. \"*\", it to matches any hub name.\r\n 2. Combine multiple hubs with \",\", for example \"hub1,hub2\", it matches \"hub1\" and \"hub2\".\r\n 3. The single hub name, for example, \"hub1\", it matches \"hub1\"."
}
},
{
"#name": "eventPattern",
"Description": {
"new": "Gets or sets the matching pattern for event names. If not set, it matches any event.\nThere are 3 kind of patterns supported:\n1. \"*\", it to matches any event name.\n2. Combine multiple events with \",\", for example \"connect,disconnect\", it matches event \"connect\" and \"disconnect\".\n3. The single event name, for example, \"connect\", it matches \"connect\".",
"old": "Gets or sets the matching pattern for event names. If not set, it matches any event.\r\nThere are 3 kind of patterns supported:\r\n 1. \"*\", it to matches any event name.\r\n 2. Combine multiple events with \",\", for example \"connect,disconnect\", it matches event \"connect\" and \"disconnect\".\r\n 3. The single event name, for example, \"connect\", it matches \"connect\"."
}
},
{
"#name": "categoryPattern",
"Description": {
"new": "Gets or sets the matching pattern for category names. If not set, it matches any category.\nThere are 3 kind of patterns supported:\n1. \"*\", it to matches any category name.\n2. Combine multiple categories with \",\", for example \"connections,messages\", it matches category \"connections\" and \"messages\".\n3. The single category name, for example, \"connections\", it matches the category \"connections\".",
"old": "Gets or sets the matching pattern for category names. If not set, it matches any category.\r\nThere are 3 kind of patterns supported:\r\n 1. \"*\", it to matches any category name.\r\n 2. Combine multiple categories with \",\", for example \"connections,messages\", it matches category \"connections\" and \"messages\".\r\n 3. The single category name, for example, \"connections\", it matches the category \"connections\"."
}
},
{
"#name": "urlTemplate",
"Description": {
"new": "Gets or sets the Upstream URL template. You can use 3 predefined parameters {hub}, {category} {event} inside the template, the value of the Upstream URL is dynamically calculated when the client request comes in.\nFor example, if the urlTemplate is `http://example.com/{hub}/api/{event}`, with a client request from hub `chat` connects, it will first POST to this URL: `http://example.com/chat/api/connect`.",
"old": "Gets or sets the Upstream URL template. You can use 3 predefined parameters {hub}, {category} {event} inside the template, the value of the Upstream URL is dynamically calculated when the client request comes in.\r\nFor example, if the urlTemplate is `http://example.com/{hub}/api/{event}`, with a client request from hub `chat` connects, it will first POST to this URL: `http://example.com/chat/api/connect`."
}
},
{
"auth": [
{
"managedIdentity": [
{
"#name": "resource",
"Description": {
"new": "The Resource indicating the App ID URI of the target resource.\nIt also appears in the aud (audience) claim of the issued token.",
"old": "The Resource indicating the App ID URI of the target resource.\r\nIt also appears in the aud (audience) claim of the issued token."
}
}
]
}
]
}
]
}
}
]
},
{
"#name": "publicNetworkAccess",
"Description": {
"new": "Enable or disable public network access. Default to \"Enabled\".\nWhen it's Enabled, network ACLs still apply.\nWhen it's Disabled, public network access is always disabled no matter what you set in network ACLs.",
"old": "Enable or disable public network access. Default to \"Enabled\".\r\nWhen it's Enabled, network ACLs still apply.\r\nWhen it's Disabled, public network access is always disabled no matter what you set in network ACLs."
}
},
{
"#name": "disableLocalAuth",
"Description": {
"new": "DisableLocalAuth\nEnable or disable local auth with AccessKey\nWhen set as true, connection with AccessKey=xxx won't work.",
"old": "DisableLocalAuth\r\nEnable or disable local auth with AccessKey\r\nWhen set as true, connection with AccessKey=xxx won't work."
}
},
{
"#name": "disableAadAuth",
"Description": {
"new": "DisableLocalAuth\nEnable or disable aad auth\nWhen set as true, connection with AuthType=aad won't work.",
"old": "DisableLocalAuth\r\nEnable or disable aad auth\r\nWhen set as true, connection with AuthType=aad won't work."
}
},
{
"#name": "regionEndpointEnabled",
"Description": {
"new": "Enable or disable the regional endpoint. Default to \"Enabled\".\nWhen it's Disabled, new connections will not be routed to this endpoint, however existing connections will not be affected.\nThis property is replica specific. Disable the regional endpoint without replica is not allowed.",
"old": "Enable or disable the regional endpoint. Default to \"Enabled\".\r\nWhen it's Disabled, new connections will not be routed to this endpoint, however existing connections will not be affected.\r\nThis property is replica specific. Disable the regional endpoint without replica is not allowed."
}
},
{
"#name": "resourceStopped",
"Description": {
"new": "Stop or start the resource. Default to \"False\".\nWhen it's true, the data plane of the resource is shutdown.\nWhen it's false, the data plane of the resource is started.",
"old": "Stop or start the resource. Default to \"False\".\r\nWhen it's true, the data plane of the resource is shutdown.\r\nWhen it's false, the data plane of the resource is started."
}
},
{
"routeSettings": [
{
"#name": "serverBalanceWeight",
"Description": {
"new": "Gets or sets the server balance weight.\nA higher value means a greater balance of client connections across different app server instances.\nA value of 0 distributes connections randomly, while a value of 255 ensures maximum balancing.\nThe default value is 255.\nRecommended ```255``` for multiple app servers in same size.",
"old": "Gets or sets the server balance weight.\r\nA higher value means a greater balance of client connections across different app server instances.\r\nA value of 0 distributes connections randomly, while a value of 255 ensures maximum balancing.\r\nThe default value is 255.\r\nRecommended ```255``` for multiple app servers in same size."
}
},
{
"#name": "connectionBalanceWeight",
"Description": {
"new": "Gets or sets the connection balance weight.\nA higher value means a greater balance of client connections across different server connections.\nA value of 0 distributes connections randomly, while a value of 255 ensures maximum balancing.\nThe default value is 255.\nRecommended ```255``` for all of the cases.",
"old": "Gets or sets the connection balance weight.\r\nA higher value means a greater balance of client connections across different server connections.\r\nA value of 0 distributes connections randomly, while a value of 255 ensures maximum balancing.\r\nThe default value is 255.\r\nRecommended ```255``` for all of the cases."
}
},
{
"#name": "latencyWeight",
"Description": {
"new": "Gets or sets the weight for latency-based routing.\nA higher value increases the influence of latency-based routing.\nA value of 0 disables latency-based routing entirely, while a value of 255 enables it fully.\nThe default value is 0.\nRecommended ```255``` for replicas or app servers in different regions for disaster recovery.",
"old": "Gets or sets the weight for latency-based routing.\r\nA higher value increases the influence of latency-based routing.\r\nA value of 0 disables latency-based routing entirely, while a value of 255 enables it fully.\r\nThe default value is 0.\r\nRecommended ```255``` for replicas or app servers in different regions for disaster recovery."
}
}
]
}
],
"sku": [
{
"#name": "name",
"Description": {
"new": "The name of the SKU. Required.\n\nAllowed values: Standard_S1, Free_F1, Premium_P1, Premium_P2",
"old": "The name of the SKU. Required.\r\n\r\nAllowed values: Standard_S1, Free_F1, Premium_P1, Premium_P2"
}
},
{
"#name": "tier",
"Description": {
"new": "Optional tier of this particular SKU. 'Standard' or 'Free'.\n\n`Basic` is deprecated, use `Standard` instead.",
"old": "Optional tier of this particular SKU. 'Standard' or 'Free'. \r\n\r\n`Basic` is deprecated, use `Standard` instead."
}
},
{
"#name": "capacity",
"Description": {
"new": "Optional, integer. The unit count of the resource.\n1 for Free_F1/Standard_S1/Premium_P1, 100 for Premium_P2 by default.\n\nIf present, following values are allowed:\nFree_F1: 1;\nStandard_S1: 1,2,3,4,5,6,7,8,9,10,20,30,40,50,60,70,80,90,100;\nPremium_P1: 1,2,3,4,5,6,7,8,9,10,20,30,40,50,60,70,80,90,100;\nPremium_P2: 100,200,300,400,500,600,700,800,900,1000;",
"old": "Optional, integer. The unit count of the resource.\r\n1 for Free_F1/Standard_S1/Premium_P1, 100 for Premium_P2 by default.\r\n\r\nIf present, following values are allowed:\r\n Free_F1: 1;\r\n Standard_S1: 1,2,3,4,5,6,7,8,9,10,20,30,40,50,60,70,80,90,100;\r\n Premium_P1: 1,2,3,4,5,6,7,8,9,10,20,30,40,50,60,70,80,90,100;\r\n Premium_P2: 100,200,300,400,500,600,700,800,900,1000;"
}
}
],
"identity": [
{
"#name": "principalId",
"Description": {
"new": "Get the principal id for the system assigned identity.\nOnly be used in response.",
"old": "Get the principal id for the system assigned identity.\r\nOnly be used in response."
}
},
{
"#name": "tenantId",
"Description": {
"new": "Get the tenant id for the system assigned identity.\nOnly be used in response",
"old": "Get the tenant id for the system assigned identity.\r\nOnly be used in response"
}
}
]
}
}
},
"$responses": {
"200": {
"Description": {
"new": "A class representing a resource.",
"old": "A class represent a resource."
},
"$properties": {
"properties": [
{
"#name": "features",
"Description": {
"new": "List of the featureFlags.\n\nFeatureFlags that are not included in the parameters for the update operation will not be modified.\nAnd the response will only include featureFlags that are explicitly set.\nWhen a featureFlag is not explicitly set, its globally default value will be used\nBut keep in mind, the default value doesn't mean \"false\". It varies in terms of different FeatureFlags.",
"old": "List of the featureFlags.\r\n\r\nFeatureFlags that are not included in the parameters for the update operation will not be modified.\r\nAnd the response will only include featureFlags that are explicitly set. \r\nWhen a featureFlag is not explicitly set, its globally default value will be used\r\nBut keep in mind, the default value doesn't mean \"false\". It varies in terms of different FeatureFlags."
},
"$items": {
"$properties": [
{
"#name": "flag",
"Description": {
"new": "FeatureFlags is the supported features of Azure SignalR service.\n- ServiceMode: Flag for backend server for SignalR service. Values allowed: \"Default\": have your own backend server; \"Serverless\": your application doesn't have a backend server; \"Classic\": for backward compatibility. Support both Default and Serverless mode but not recommended; \"PredefinedOnly\": for future use.\n- EnableConnectivityLogs: \"true\"/\"false\", to enable/disable the connectivity log category respectively.\n- EnableMessagingLogs: \"true\"/\"false\", to enable/disable the connectivity log category respectively.\n- EnableLiveTrace: Live Trace allows you to know what's happening inside Azure SignalR service, it will give you live traces in real time, it will be helpful when you developing your own Azure SignalR based web application or self-troubleshooting some issues. Please note that live traces are counted as outbound messages that will be charged. Values allowed: \"true\"/\"false\", to enable/disable live trace feature.",
"old": "FeatureFlags is the supported features of Azure SignalR service.\r\n- ServiceMode: Flag for backend server for SignalR service. Values allowed: \"Default\": have your own backend server; \"Serverless\": your application doesn't have a backend server; \"Classic\": for backward compatibility. Support both Default and Serverless mode but not recommended; \"PredefinedOnly\": for future use.\r\n- EnableConnectivityLogs: \"true\"/\"false\", to enable/disable the connectivity log category respectively.\r\n- EnableMessagingLogs: \"true\"/\"false\", to enable/disable the connectivity log category respectively.\r\n- EnableLiveTrace: Live Trace allows you to know what's happening inside Azure SignalR service, it will give you live traces in real time, it will be helpful when you developing your own Azure SignalR based web application or self-troubleshooting some issues. Please note that live traces are counted as outbound messages that will be charged. Values allowed: \"true\"/\"false\", to enable/disable live trace feature."
}
}
]
}
},
{
"liveTraceConfiguration": [
{
"#name": "enabled",
"Description": {
"new": "Indicates whether or not enable live trace.\nWhen it's set to true, live trace client can connect to the service.\nOtherwise, live trace client can't connect to the service, so that you are unable to receive any log, no matter what you configure in \"categories\".\nAvailable values: true, false.\nCase insensitive.",
"old": "Indicates whether or not enable live trace.\r\nWhen it's set to true, live trace client can connect to the service.\r\nOtherwise, live trace client can't connect to the service, so that you are unable to receive any log, no matter what you configure in \"categories\".\r\nAvailable values: true, false.\r\nCase insensitive."
}
},
{
"categories": {
"$properties": [
{
"#name": "name",
"Description": {
"new": "Gets or sets the live trace category's name.\nAvailable values: ConnectivityLogs, MessagingLogs.\nCase insensitive.",
"old": "Gets or sets the live trace category's name.\r\nAvailable values: ConnectivityLogs, MessagingLogs.\r\nCase insensitive."
}
},
{
"#name": "enabled",
"Description": {
"new": "Indicates whether or the live trace category is enabled.\nAvailable values: true, false.\nCase insensitive.",
"old": "Indicates whether or the live trace category is enabled.\r\nAvailable values: true, false.\r\nCase insensitive."
}
}
]
}
}
]
},
{
"resourceLogConfiguration": [
{
"categories": {
"$properties": [
{
"#name": "name",
"Description": {
"new": "Gets or sets the resource log category's name.\nAvailable values: ConnectivityLogs, MessagingLogs.\nCase insensitive.",
"old": "Gets or sets the resource log category's name.\r\nAvailable values: ConnectivityLogs, MessagingLogs.\r\nCase insensitive."
}
},
{
"#name": "enabled",
"Description": {
"new": "Indicates whether or the resource log category is enabled.\nAvailable values: true, false.\nCase insensitive.",
"old": "Indicates whether or the resource log category is enabled.\r\nAvailable values: true, false.\r\nCase insensitive."
}
}
]
}
}
]
},
{
"serverless": [
{
"#name": "connectionTimeoutInSeconds",
"Description": {
"new": "Gets or sets Client Connection Timeout. Optional to be set.\nValue in seconds.\nDefault value is 30 seconds.\nCustomer should set the timeout to a shorter period if messages are expected to be sent in shorter intervals,\nand want the client to disconnect more quickly after the last message is sent.\nYou can set the timeout to a longer period if messages are expected to be sent in longer intervals,\nand they want to keep the same client connection alive during this session.\nThe service considers the client disconnected if it hasn't received a message (including keep-alive) in this interval.",
"old": "Gets or sets Client Connection Timeout. Optional to be set.\r\nValue in seconds.\r\nDefault value is 30 seconds.\r\nCustomer should set the timeout to a shorter period if messages are expected to be sent in shorter intervals,\r\nand want the client to disconnect more quickly after the last message is sent.\r\nYou can set the timeout to a longer period if messages are expected to be sent in longer intervals,\r\nand they want to keep the same client connection alive during this session.\r\nThe service considers the client disconnected if it hasn't received a message (including keep-alive) in this interval."
}
},
{
"#name": "keepAliveIntervalInSeconds",
"Description": {
"new": "Gets or sets the Keep-Alive Interval. Optional to set.\nValue is in seconds.\nThe default value is 15 seconds.\nCustomers should set this value to a shorter period if they want the service to send keep-alive messages more frequently,\nensuring timely checks of the connection status.\nConversely, customers can set this value to a longer period if they want the service to send keep-alive messages less frequently,\nreducing network traffic, but note that it may take longer to detect a disconnection.\nThis interval ensures that the connection is maintained by sending periodic keep-alive messages to the client.",
"old": "Gets or sets the Keep-Alive Interval. Optional to set.\r\nValue is in seconds.\r\nThe default value is 15 seconds.\r\nCustomers should set this value to a shorter period if they want the service to send keep-alive messages more frequently, \r\nensuring timely checks of the connection status.\r\nConversely, customers can set this value to a longer period if they want the service to send keep-alive messages less frequently, \r\nreducing network traffic, but note that it may take longer to detect a disconnection.\r\nThis interval ensures that the connection is maintained by sending periodic keep-alive messages to the client."
}
}
]
},
{
"upstream": [
{
"templates": {
"Description": {
"new": "Upstream template item settings. It defines the Upstream URL of the incoming requests.\nThe template defines the pattern of the event, the hub or the category of the incoming request that matches current URL template.",
"old": "Upstream template item settings. It defines the Upstream URL of the incoming requests.\r\nThe template defines the pattern of the event, the hub or the category of the incoming request that matches current URL template."
},
"$properties": [
{
"#name": "hubPattern",
"Description": {
"new": "Gets or sets the matching pattern for hub names. If not set, it matches any hub.\nThere are 3 kind of patterns supported:\n1. \"*\", it to matches any hub name.\n2. Combine multiple hubs with \",\", for example \"hub1,hub2\", it matches \"hub1\" and \"hub2\".\n3. The single hub name, for example, \"hub1\", it matches \"hub1\".",
"old": "Gets or sets the matching pattern for hub names. If not set, it matches any hub.\r\nThere are 3 kind of patterns supported:\r\n 1. \"*\", it to matches any hub name.\r\n 2. Combine multiple hubs with \",\", for example \"hub1,hub2\", it matches \"hub1\" and \"hub2\".\r\n 3. The single hub name, for example, \"hub1\", it matches \"hub1\"."
}
},
{
"#name": "eventPattern",
"Description": {
"new": "Gets or sets the matching pattern for event names. If not set, it matches any event.\nThere are 3 kind of patterns supported:\n1. \"*\", it to matches any event name.\n2. Combine multiple events with \",\", for example \"connect,disconnect\", it matches event \"connect\" and \"disconnect\".\n3. The single event name, for example, \"connect\", it matches \"connect\".",
"old": "Gets or sets the matching pattern for event names. If not set, it matches any event.\r\nThere are 3 kind of patterns supported:\r\n 1. \"*\", it to matches any event name.\r\n 2. Combine multiple events with \",\", for example \"connect,disconnect\", it matches event \"connect\" and \"disconnect\".\r\n 3. The single event name, for example, \"connect\", it matches \"connect\"."
}
},
{
"#name": "categoryPattern",
"Description": {
"new": "Gets or sets the matching pattern for category names. If not set, it matches any category.\nThere are 3 kind of patterns supported:\n1. \"*\", it to matches any category name.\n2. Combine multiple categories with \",\", for example \"connections,messages\", it matches category \"connections\" and \"messages\".\n3. The single category name, for example, \"connections\", it matches the category \"connections\".",
"old": "Gets or sets the matching pattern for category names. If not set, it matches any category.\r\nThere are 3 kind of patterns supported:\r\n 1. \"*\", it to matches any category name.\r\n 2. Combine multiple categories with \",\", for example \"connections,messages\", it matches category \"connections\" and \"messages\".\r\n 3. The single category name, for example, \"connections\", it matches the category \"connections\"."
}
},
{
"#name": "urlTemplate",
"Description": {
"new": "Gets or sets the Upstream URL template. You can use 3 predefined parameters {hub}, {category} {event} inside the template, the value of the Upstream URL is dynamically calculated when the client request comes in.\nFor example, if the urlTemplate is `http://example.com/{hub}/api/{event}`, with a client request from hub `chat` connects, it will first POST to this URL: `http://example.com/chat/api/connect`.",
"old": "Gets or sets the Upstream URL template. You can use 3 predefined parameters {hub}, {category} {event} inside the template, the value of the Upstream URL is dynamically calculated when the client request comes in.\r\nFor example, if the urlTemplate is `http://example.com/{hub}/api/{event}`, with a client request from hub `chat` connects, it will first POST to this URL: `http://example.com/chat/api/connect`."
}
},
{
"auth": [
{
"managedIdentity": [
{
"#name": "resource",
"Description": {
"new": "The Resource indicating the App ID URI of the target resource.\nIt also appears in the aud (audience) claim of the issued token.",
"old": "The Resource indicating the App ID URI of the target resource.\r\nIt also appears in the aud (audience) claim of the issued token."
}
}
]
}
]
}
]
}
}
]
},
{
"#name": "publicNetworkAccess",
"Description": {
"new": "Enable or disable public network access. Default to \"Enabled\".\nWhen it's Enabled, network ACLs still apply.\nWhen it's Disabled, public network access is always disabled no matter what you set in network ACLs.",
"old": "Enable or disable public network access. Default to \"Enabled\".\r\nWhen it's Enabled, network ACLs still apply.\r\nWhen it's Disabled, public network access is always disabled no matter what you set in network ACLs."
}
},
{
"#name": "disableLocalAuth",
"Description": {
"new": "DisableLocalAuth\nEnable or disable local auth with AccessKey\nWhen set as true, connection with AccessKey=xxx won't work.",
"old": "DisableLocalAuth\r\nEnable or disable local auth with AccessKey\r\nWhen set as true, connection with AccessKey=xxx won't work."
}
},
{
"#name": "disableAadAuth",
"Description": {
"new": "DisableLocalAuth\nEnable or disable aad auth\nWhen set as true, connection with AuthType=aad won't work.",
"old": "DisableLocalAuth\r\nEnable or disable aad auth\r\nWhen set as true, connection with AuthType=aad won't work."
}
},
{
"#name": "regionEndpointEnabled",
"Description": {
"new": "Enable or disable the regional endpoint. Default to \"Enabled\".\nWhen it's Disabled, new connections will not be routed to this endpoint, however existing connections will not be affected.\nThis property is replica specific. Disable the regional endpoint without replica is not allowed.",
"old": "Enable or disable the regional endpoint. Default to \"Enabled\".\r\nWhen it's Disabled, new connections will not be routed to this endpoint, however existing connections will not be affected.\r\nThis property is replica specific. Disable the regional endpoint without replica is not allowed."
}
},
{
"#name": "resourceStopped",
"Description": {
"new": "Stop or start the resource. Default to \"False\".\nWhen it's true, the data plane of the resource is shutdown.\nWhen it's false, the data plane of the resource is started.",
"old": "Stop or start the resource. Default to \"False\".\r\nWhen it's true, the data plane of the resource is shutdown.\r\nWhen it's false, the data plane of the resource is started."
}
},
{
"routeSettings": [
{
"#name": "serverBalanceWeight",
"Description": {
"new": "Gets or sets the server balance weight.\nA higher value means a greater balance of client connections across different app server instances.\nA value of 0 distributes connections randomly, while a value of 255 ensures maximum balancing.\nThe default value is 255.\nRecommended ```255``` for multiple app servers in same size.",
"old": "Gets or sets the server balance weight.\r\nA higher value means a greater balance of client connections across different app server instances.\r\nA value of 0 distributes connections randomly, while a value of 255 ensures maximum balancing.\r\nThe default value is 255.\r\nRecommended ```255``` for multiple app servers in same size."
}
},
{
"#name": "connectionBalanceWeight",
"Description": {
"new": "Gets or sets the connection balance weight.\nA higher value means a greater balance of client connections across different server connections.\nA value of 0 distributes connections randomly, while a value of 255 ensures maximum balancing.\nThe default value is 255.\nRecommended ```255``` for all of the cases.",
"old": "Gets or sets the connection balance weight.\r\nA higher value means a greater balance of client connections across different server connections.\r\nA value of 0 distributes connections randomly, while a value of 255 ensures maximum balancing.\r\nThe default value is 255.\r\nRecommended ```255``` for all of the cases."
}
},
{
"#name": "latencyWeight",
"Description": {
"new": "Gets or sets the weight for latency-based routing.\nA higher value increases the influence of latency-based routing.\nA value of 0 disables latency-based routing entirely, while a value of 255 enables it fully.\nThe default value is 0.\nRecommended ```255``` for replicas or app servers in different regions for disaster recovery.",
"old": "Gets or sets the weight for latency-based routing.\r\nA higher value increases the influence of latency-based routing.\r\nA value of 0 disables latency-based routing entirely, while a value of 255 enables it fully.\r\nThe default value is 0.\r\nRecommended ```255``` for replicas or app servers in different regions for disaster recovery."
}
}
]
}
],
"sku": [
{
"#name": "name",
"Description": {
"new": "The name of the SKU. Required.\n\nAllowed values: Standard_S1, Free_F1, Premium_P1, Premium_P2",
"old": "The name of the SKU. Required.\r\n\r\nAllowed values: Standard_S1, Free_F1, Premium_P1, Premium_P2"
}
},
{
"#name": "tier",
"Description": {
"new": "Optional tier of this particular SKU. 'Standard' or 'Free'.\n\n`Basic` is deprecated, use `Standard` instead.",
"old": "Optional tier of this particular SKU. 'Standard' or 'Free'. \r\n\r\n`Basic` is deprecated, use `Standard` instead."
}
},
{
"#name": "capacity",
"Description": {
"new": "Optional, integer. The unit count of the resource.\n1 for Free_F1/Standard_S1/Premium_P1, 100 for Premium_P2 by default.\n\nIf present, following values are allowed:\nFree_F1: 1;\nStandard_S1: 1,2,3,4,5,6,7,8,9,10,20,30,40,50,60,70,80,90,100;\nPremium_P1: 1,2,3,4,5,6,7,8,9,10,20,30,40,50,60,70,80,90,100;\nPremium_P2: 100,200,300,400,500,600,700,800,900,1000;",
"old": "Optional, integer. The unit count of the resource.\r\n1 for Free_F1/Standard_S1/Premium_P1, 100 for Premium_P2 by default.\r\n\r\nIf present, following values are allowed:\r\n Free_F1: 1;\r\n Standard_S1: 1,2,3,4,5,6,7,8,9,10,20,30,40,50,60,70,80,90,100;\r\n Premium_P1: 1,2,3,4,5,6,7,8,9,10,20,30,40,50,60,70,80,90,100;\r\n Premium_P2: 100,200,300,400,500,600,700,800,900,1000;"
}
}
],
"identity": [
{
"#name": "principalId",
"Description": {
"new": "Get the principal id for the system assigned identity.\nOnly be used in response.",
"old": "Get the principal id for the system assigned identity.\r\nOnly be used in response."
}
},
{
"#name": "tenantId",
"Description": {
"new": "Get the tenant id for the system assigned identity.\nOnly be used in response",
"old": "Get the tenant id for the system assigned identity.\r\nOnly be used in response"
}
}
]
}
},
"201": {
"Description": {
"new": "A class representing a resource.",
"old": "A class represent a resource."
},
"$properties": {
"properties": [
{
"#name": "features",
"Description": {
"new": "List of the featureFlags.\n\nFeatureFlags that are not included in the parameters for the update operation will not be modified.\nAnd the response will only include featureFlags that are explicitly set.\nWhen a featureFlag is not explicitly set, its globally default value will be used\nBut keep in mind, the default value doesn't mean \"false\". It varies in terms of different FeatureFlags.",
"old": "List of the featureFlags.\r\n\r\nFeatureFlags that are not included in the parameters for the update operation will not be modified.\r\nAnd the response will only include featureFlags that are explicitly set. \r\nWhen a featureFlag is not explicitly set, its globally default value will be used\r\nBut keep in mind, the default value doesn't mean \"false\". It varies in terms of different FeatureFlags."
},
"$items": {
"$properties": [
{
"#name": "flag",
"Description": {
"new": "FeatureFlags is the supported features of Azure SignalR service.\n- ServiceMode: Flag for backend server for SignalR service. Values allowed: \"Default\": have your own backend server; \"Serverless\": your application doesn't have a backend server; \"Classic\": for backward compatibility. Support both Default and Serverless mode but not recommended; \"PredefinedOnly\": for future use.\n- EnableConnectivityLogs: \"true\"/\"false\", to enable/disable the connectivity log category respectively.\n- EnableMessagingLogs: \"true\"/\"false\", to enable/disable the connectivity log category respectively.\n- EnableLiveTrace: Live Trace allows you to know what's happening inside Azure SignalR service, it will give you live traces in real time, it will be helpful when you developing your own Azure SignalR based web application or self-troubleshooting some issues. Please note that live traces are counted as outbound messages that will be charged. Values allowed: \"true\"/\"false\", to enable/disable live trace feature.",
"old": "FeatureFlags is the supported features of Azure SignalR service.\r\n- ServiceMode: Flag for backend server for SignalR service. Values allowed: \"Default\": have your own backend server; \"Serverless\": your application doesn't have a backend server; \"Classic\": for backward compatibility. Support both Default and Serverless mode but not recommended; \"PredefinedOnly\": for future use.\r\n- EnableConnectivityLogs: \"true\"/\"false\", to enable/disable the connectivity log category respectively.\r\n- EnableMessagingLogs: \"true\"/\"false\", to enable/disable the connectivity log category respectively.\r\n- EnableLiveTrace: Live Trace allows you to know what's happening inside Azure SignalR service, it will give you live traces in real time, it will be helpful when you developing your own Azure SignalR based web application or self-troubleshooting some issues. Please note that live traces are counted as outbound messages that will be charged. Values allowed: \"true\"/\"false\", to enable/disable live trace feature."
}
}
]
}
},
{
"liveTraceConfiguration": [
{
"#name": "enabled",
"Description": {
"new": "Indicates whether or not enable live trace.\nWhen it's set to true, live trace client can connect to the service.\nOtherwise, live trace client can't connect to the service, so that you are unable to receive any log, no matter what you configure in \"categories\".\nAvailable values: true, false.\nCase insensitive.",
"old": "Indicates whether or not enable live trace.\r\nWhen it's set to true, live trace client can connect to the service.\r\nOtherwise, live trace client can't connect to the service, so that you are unable to receive any log, no matter what you configure in \"categories\".\r\nAvailable values: true, false.\r\nCase insensitive."
}
},
{
"categories": {
"$properties": [
{
"#name": "name",
"Description": {
"new": "Gets or sets the live trace category's name.\nAvailable values: ConnectivityLogs, MessagingLogs.\nCase insensitive.",
"old": "Gets or sets the live trace category's name.\r\nAvailable values: ConnectivityLogs, MessagingLogs.\r\nCase insensitive."
}
},
{
"#name": "enabled",
"Description": {
"new": "Indicates whether or the live trace category is enabled.\nAvailable values: true, false.\nCase insensitive.",
"old": "Indicates whether or the live trace category is enabled.\r\nAvailable values: true, false.\r\nCase insensitive."
}
}
]
}
}
]
},
{
"resourceLogConfiguration": [
{
"categories": {
"$properties": [
{
"#name": "name",
"Description": {
"new": "Gets or sets the resource log category's name.\nAvailable values: ConnectivityLogs, MessagingLogs.\nCase insensitive.",
"old": "Gets or sets the resource log category's name.\r\nAvailable values: ConnectivityLogs, MessagingLogs.\r\nCase insensitive."
}
},
{
"#name": "enabled",
"Description": {
"new": "Indicates whether or the resource log category is enabled.\nAvailable values: true, false.\nCase insensitive.",
"old": "Indicates whether or the resource log category is enabled.\r\nAvailable values: true, false.\r\nCase insensitive."
}
}
]
}
}
]
},
{
"serverless": [
{
"#name": "connectionTimeoutInSeconds",
"Description": {
"new": "Gets or sets Client Connection Timeout. Optional to be set.\nValue in seconds.\nDefault value is 30 seconds.\nCustomer should set the timeout to a shorter period if messages are expected to be sent in shorter intervals,\nand want the client to disconnect more quickly after the last message is sent.\nYou can set the timeout to a longer period if messages are expected to be sent in longer intervals,\nand they want to keep the same client connection alive during this session.\nThe service considers the client disconnected if it hasn't received a message (including keep-alive) in this interval.",
"old": "Gets or sets Client Connection Timeout. Optional to be set.\r\nValue in seconds.\r\nDefault value is 30 seconds.\r\nCustomer should set the timeout to a shorter period if messages are expected to be sent in shorter intervals,\r\nand want the client to disconnect more quickly after the last message is sent.\r\nYou can set the timeout to a longer period if messages are expected to be sent in longer intervals,\r\nand they want to keep the same client connection alive during this session.\r\nThe service considers the client disconnected if it hasn't received a message (including keep-alive) in this interval."
}
},
{
"#name": "keepAliveIntervalInSeconds",
"Description": {
"new": "Gets or sets the Keep-Alive Interval. Optional to set.\nValue is in seconds.\nThe default value is 15 seconds.\nCustomers should set this value to a shorter period if they want the service to send keep-alive messages more frequently,\nensuring timely checks of the connection status.\nConversely, customers can set this value to a longer period if they want the service to send keep-alive messages less frequently,\nreducing network traffic, but note that it may take longer to detect a disconnection.\nThis interval ensures that the connection is maintained by sending periodic keep-alive messages to the client.",
"old": "Gets or sets the Keep-Alive Interval. Optional to set.\r\nValue is in seconds.\r\nThe default value is 15 seconds.\r\nCustomers should set this value to a shorter period if they want the service to send keep-alive messages more frequently, \r\nensuring timely checks of the connection status.\r\nConversely, customers can set this value to a longer period if they want the service to send keep-alive messages less frequently, \r\nreducing network traffic, but note that it may take longer to detect a disconnection.\r\nThis interval ensures that the connection is maintained by sending periodic keep-alive messages to the client."
}
}
]
},
{
"upstream": [
{
"templates": {
"Description": {
"new": "Upstream template item settings. It defines the Upstream URL of the incoming requests.\nThe template defines the pattern of the event, the hub or the category of the incoming request that matches current URL template.",
"old": "Upstream template item settings. It defines the Upstream URL of the incoming requests.\r\nThe template defines the pattern of the event, the hub or the category of the incoming request that matches current URL template."
},
"$properties": [
{
"#name": "hubPattern",
"Description": {
"new": "Gets or sets the matching pattern for hub names. If not set, it matches any hub.\nThere are 3 kind of patterns supported:\n1. \"*\", it to matches any hub name.\n2. Combine multiple hubs with \",\", for example \"hub1,hub2\", it matches \"hub1\" and \"hub2\".\n3. The single hub name, for example, \"hub1\", it matches \"hub1\".",
"old": "Gets or sets the matching pattern for hub names. If not set, it matches any hub.\r\nThere are 3 kind of patterns supported:\r\n 1. \"*\", it to matches any hub name.\r\n 2. Combine multiple hubs with \",\", for example \"hub1,hub2\", it matches \"hub1\" and \"hub2\".\r\n 3. The single hub name, for example, \"hub1\", it matches \"hub1\"."
}
},
{
"#name": "eventPattern",
"Description": {
"new": "Gets or sets the matching pattern for event names. If not set, it matches any event.\nThere are 3 kind of patterns supported:\n1. \"*\", it to matches any event name.\n2. Combine multiple events with \",\", for example \"connect,disconnect\", it matches event \"connect\" and \"disconnect\".\n3. The single event name, for example, \"connect\", it matches \"connect\".",
"old": "Gets or sets the matching pattern for event names. If not set, it matches any event.\r\nThere are 3 kind of patterns supported:\r\n 1. \"*\", it to matches any event name.\r\n 2. Combine multiple events with \",\", for example \"connect,disconnect\", it matches event \"connect\" and \"disconnect\".\r\n 3. The single event name, for example, \"connect\", it matches \"connect\"."
}
},
{
"#name": "categoryPattern",
"Description": {
"new": "Gets or sets the matching pattern for category names. If not set, it matches any category.\nThere are 3 kind of patterns supported:\n1. \"*\", it to matches any category name.\n2. Combine multiple categories with \",\", for example \"connections,messages\", it matches category \"connections\" and \"messages\".\n3. The single category name, for example, \"connections\", it matches the category \"connections\".",
"old": "Gets or sets the matching pattern for category names. If not set, it matches any category.\r\nThere are 3 kind of patterns supported:\r\n 1. \"*\", it to matches any category name.\r\n 2. Combine multiple categories with \",\", for example \"connections,messages\", it matches category \"connections\" and \"messages\".\r\n 3. The single category name, for example, \"connections\", it matches the category \"connections\"."
}
},
{
"#name": "urlTemplate",
"Description": {
"new": "Gets or sets the Upstream URL template. You can use 3 predefined parameters {hub}, {category} {event} inside the template, the value of the Upstream URL is dynamically calculated when the client request comes in.\nFor example, if the urlTemplate is `http://example.com/{hub}/api/{event}`, with a client request from hub `chat` connects, it will first POST to this URL: `http://example.com/chat/api/connect`.",
"old": "Gets or sets the Upstream URL template. You can use 3 predefined parameters {hub}, {category} {event} inside the template, the value of the Upstream URL is dynamically calculated when the client request comes in.\r\nFor example, if the urlTemplate is `http://example.com/{hub}/api/{event}`, with a client request from hub `chat` connects, it will first POST to this URL: `http://example.com/chat/api/connect`."
}
},
{
"auth": [
{
"managedIdentity": [
{
"#name": "resource",
"Description": {
"new": "The Resource indicating the App ID URI of the target resource.\nIt also appears in the aud (audience) claim of the issued token.",
"old": "The Resource indicating the App ID URI of the target resource.\r\nIt also appears in the aud (audience) claim of the issued token."
}
}
]
}
]
}
]
}
}
]
},
{
"#name": "publicNetworkAccess",
"Description": {
"new": "Enable or disable public network access. Default to \"Enabled\".\nWhen it's Enabled, network ACLs still apply.\nWhen it's Disabled, public network access is always disabled no matter what you set in network ACLs.",
"old": "Enable or disable public network access. Default to \"Enabled\".\r\nWhen it's Enabled, network ACLs still apply.\r\nWhen it's Disabled, public network access is always disabled no matter what you set in network ACLs."
}
},
{
"#name": "disableLocalAuth",
"Description": {
"new": "DisableLocalAuth\nEnable or disable local auth with AccessKey\nWhen set as true, connection with AccessKey=xxx won't work.",
"old": "DisableLocalAuth\r\nEnable or disable local auth with AccessKey\r\nWhen set as true, connection with AccessKey=xxx won't work."
}
},
{
"#name": "disableAadAuth",
"Description": {
"new": "DisableLocalAuth\nEnable or disable aad auth\nWhen set as true, connection with AuthType=aad won't work.",
"old": "DisableLocalAuth\r\nEnable or disable aad auth\r\nWhen set as true, connection with AuthType=aad won't work."
}
},
{
"#name": "regionEndpointEnabled",
"Description": {
"new": "Enable or disable the regional endpoint. Default to \"Enabled\".\nWhen it's Disabled, new connections will not be routed to this endpoint, however existing connections will not be affected.\nThis property is replica specific. Disable the regional endpoint without replica is not allowed.",
"old": "Enable or disable the regional endpoint. Default to \"Enabled\".\r\nWhen it's Disabled, new connections will not be routed to this endpoint, however existing connections will not be affected.\r\nThis property is replica specific. Disable the regional endpoint without replica is not allowed."
}
},
{
"#name": "resourceStopped",
"Description": {
"new": "Stop or start the resource. Default to \"False\".\nWhen it's true, the data plane of the resource is shutdown.\nWhen it's false, the data plane of the resource is started.",
"old": "Stop or start the resource. Default to \"False\".\r\nWhen it's true, the data plane of the resource is shutdown.\r\nWhen it's false, the data plane of the resource is started."
}
},
{
"routeSettings": [
{
"#name": "serverBalanceWeight",
"Description": {
"new": "Gets or sets the server balance weight.\nA higher value means a greater balance of client connections across different app server instances.\nA value of 0 distributes connections randomly, while a value of 255 ensures maximum balancing.\nThe default value is 255.\nRecommended ```255``` for multiple app servers in same size.",
"old": "Gets or sets the server balance weight.\r\nA higher value means a greater balance of client connections across different app server instances.\r\nA value of 0 distributes connections randomly, while a value of 255 ensures maximum balancing.\r\nThe default value is 255.\r\nRecommended ```255``` for multiple app servers in same size."
}
},
{
"#name": "connectionBalanceWeight",
"Description": {
"new": "Gets or sets the connection balance weight.\nA higher value means a greater balance of client connections across different server connections.\nA value of 0 distributes connections randomly, while a value of 255 ensures maximum balancing.\nThe default value is 255.\nRecommended ```255``` for all of the cases.",
"old": "Gets or sets the connection balance weight.\r\nA higher value means a greater balance of client connections across different server connections.\r\nA value of 0 distributes connections randomly, while a value of 255 ensures maximum balancing.\r\nThe default value is 255.\r\nRecommended ```255``` for all of the cases."
}
},
{
"#name": "latencyWeight",
"Description": {
"new": "Gets or sets the weight for latency-based routing.\nA higher value increases the influence of latency-based routing.\nA value of 0 disables latency-based routing entirely, while a value of 255 enables it fully.\nThe default value is 0.\nRecommended ```255``` for replicas or app servers in different regions for disaster recovery.",
"old": "Gets or sets the weight for latency-based routing.\r\nA higher value increases the influence of latency-based routing.\r\nA value of 0 disables latency-based routing entirely, while a value of 255 enables it fully.\r\nThe default value is 0.\r\nRecommended ```255``` for replicas or app servers in different regions for disaster recovery."
}
}
]
}
],
"sku": [
{
"#name": "name",
"Description": {
"new": "The name of the SKU. Required.\n\nAllowed values: Standard_S1, Free_F1, Premium_P1, Premium_P2",
"old": "The name of the SKU. Required.\r\n\r\nAllowed values: Standard_S1, Free_F1, Premium_P1, Premium_P2"
}
},
{
"#name": "tier",
"Description": {
"new": "Optional tier of this particular SKU. 'Standard' or 'Free'.\n\n`Basic` is deprecated, use `Standard` instead.",
"old": "Optional tier of this particular SKU. 'Standard' or 'Free'. \r\n\r\n`Basic` is deprecated, use `Standard` instead."
}
},
{
"#name": "capacity",
"Description": {
"new": "Optional, integer. The unit count of the resource.\n1 for Free_F1/Standard_S1/Premium_P1, 100 for Premium_P2 by default.\n\nIf present, following values are allowed:\nFree_F1: 1;\nStandard_S1: 1,2,3,4,5,6,7,8,9,10,20,30,40,50,60,70,80,90,100;\nPremium_P1: 1,2,3,4,5,6,7,8,9,10,20,30,40,50,60,70,80,90,100;\nPremium_P2: 100,200,300,400,500,600,700,800,900,1000;",
"old": "Optional, integer. The unit count of the resource.\r\n1 for Free_F1/Standard_S1/Premium_P1, 100 for Premium_P2 by default.\r\n\r\nIf present, following values are allowed:\r\n Free_F1: 1;\r\n Standard_S1: 1,2,3,4,5,6,7,8,9,10,20,30,40,50,60,70,80,90,100;\r\n Premium_P1: 1,2,3,4,5,6,7,8,9,10,20,30,40,50,60,70,80,90,100;\r\n Premium_P2: 100,200,300,400,500,600,700,800,900,1000;"
}
}
],
"identity": [
{
"#name": "principalId",
"Description": {
"new": "Get the principal id for the system assigned identity.\nOnly be used in response.",
"old": "Get the principal id for the system assigned identity.\r\nOnly be used in response."
}
},
{
"#name": "tenantId",
"Description": {
"new": "Get the tenant id for the system assigned identity.\nOnly be used in response",
"old": "Get the tenant id for the system assigned identity.\r\nOnly be used in response"
}
}
]
}
}
}
}