You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/notification-hubs/notification-hubs-tags-segment-push-message.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ The only way to target specific notification registrations is to associate tags
35
35
36
36
## Tags
37
37
38
-
A tag can be any string, up to 120 characters, containing alphanumeric and the following non-alphanumeric characters: ‘`_`’, ‘`@`’, ‘`#`’, ‘`.`’, ‘`:`’, ‘`-`’. The following example shows an application from which you can receive toast notifications about specific music groups. In this scenario, a simple way to route notifications is to label registrations with tags that represent the different bands, as in the following figure:
38
+
A tag can be any string, up to 120 characters, containing alphanumeric and the following non-alphanumeric characters: '`_`', '`@`', '`#`', '`.`', '`:`', '`-`'. The following example shows an application from which you can receive toast notifications about specific music groups. In this scenario, a simple way to route notifications is to label registrations with tags that represent the different bands, as in the following figure:
In this example, Alice is interested in updates for the Beatles, and Bob is interested in updates for the Wailers. Bob is also interested in Charlie’s comments, and Charlie is interested in the Wailers. When a notification is sent for Charlie’s comment on the Beatles, Notification Hubs sends it to both Alice and Bob.
66
+
In this example, Alice is interested in updates for the Beatles, and Bob is interested in updates for the Wailers. Bob is also interested in Charlie's comments, and Charlie is interested in the Wailers. When a notification is sent for Charlie's comment on the Beatles, Notification Hubs sends it to both Alice and Bob.
67
67
68
68
While you can encode multiple concerns in tags (for example, `band_Beatles` or `follows_Charlie`), tags are simple strings and not properties with values. A registration matches only on the presence or absence of a specific tag.
69
69
@@ -92,7 +92,7 @@ Consider a sports application that sends a reminder to everyone in Boston about
Tag expressions support common Boolean operators such as `AND` (`&&`), `OR` (`||`), and `NOT` (`!`); they can also contain parentheses. Tag expressions using only `OR` operators can reference 20 tags; otherwise tag expressions are limited to 6 tags.
95
+
Tag expressions support common Boolean operators such as `AND` (`&&`), `OR` (`||`), and `NOT` (`!`); they can also contain parentheses. Tag expressions using only `OR` operators can reference 20 tags; expression with `AND` operators but no `OR` operators can reference 10 tags; otherwise, tag expressions are limited to 6 tags.
96
96
97
97
Here's an example for sending notifications with tag expressions using the SDK:
This article shows how to use an Azure Resource Manager template that creates a Service Bus namespace and a queue within that namespace. The article explains how to specify which resources are deployed and how to define parameters that are specified when the deployment is executed. You can use this template for your own deployments, or customize it to meet your requirements.
23
24
24
-
For more information about creating templates, please see [Authoring Azure Resource Manager templates][Authoring Azure Resource Manager templates].
For the complete template, see the [Service Bus namespace and queue template][Service Bus namespace and queue template] on GitHub.
27
+
If you don't have an Azure subscription, [create a free account](https://azure.microsoft.com/free/) before you begin.
28
+
29
+
## Prerequisites
30
+
31
+
None
32
+
33
+
## Create a Service Bus namespace and a queue
34
+
35
+
### Review the template
36
+
37
+
The template used in this quickstart is from [Azure Quickstart templates](https://azure.microsoft.com/resources/templates/201-servicebus-create-queue).
You can find more template from [Azure Quickstart templates](https://azure.microsoft.com/resources/templates/?resourceType=Microsoft.Servicebus&pageNumber=1&sort=Popular)
39
55
40
-
##What will you deploy?
56
+
### Deploy the template
41
57
42
58
With this template, you deploy a Service Bus namespace with a queue.
43
59
@@ -47,95 +63,9 @@ To run the deployment automatically, click the following button:
47
63
48
64
[](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2F201-servicebus-create-queue%2Fazuredeploy.json)
49
65
50
-
## Parameters
51
-
52
-
With Azure Resource Manager, you define parameters for values you want to specify when the template is deployed. The template includes a section called `Parameters` that contains all of the parameter values. You should define a parameter for those values that will vary based on the project you are deploying or based on the environment you are deploying to. Do not define parameters for values that will always stay the same. Each parameter value is used in the template to define the resources that are deployed.
53
-
54
-
The template defines the following parameters.
55
-
56
-
### serviceBusNamespaceName
57
-
The name of the Service Bus namespace to create.
58
-
59
-
```json
60
-
"serviceBusNamespaceName": {
61
-
"type": "string",
62
-
"metadata": {
63
-
"description": "Name of the Service Bus namespace"
64
-
}
65
-
}
66
-
```
67
-
68
-
### serviceBusQueueName
69
-
The name of the queue created in the Service Bus namespace.
70
-
71
-
```json
72
-
"serviceBusQueueName": {
73
-
"type": "string"
74
-
}
75
-
```
76
-
77
-
### serviceBusApiVersion
78
-
The Service Bus API version of the template.
79
-
80
-
```json
81
-
"serviceBusApiVersion": {
82
-
"type": "string",
83
-
"defaultValue": "2017-04-01",
84
-
"metadata": {
85
-
"description": "Service Bus ApiVersion used by the template"
86
-
}
87
-
```
88
-
89
-
## Resources to deploy
90
-
Creates a standard Service Bus namespace of type **Messaging**, with a queue.
For JSON syntax and properties, see [namespaces](/azure/templates/microsoft.servicebus/namespaces) and [queues](/azure/templates/microsoft.servicebus/namespaces/queues).
azure group deployment create \<my-resource-group\> \<my-deployment-name\> --template-uri <https://raw.githubusercontent.com/azure/azure-quickstart-templates/master/201-servicebus-create-queue/azuredeploy.json>
135
-
```
136
-
137
66
## Next steps
138
-
See the following topic that shows how to create an authorization rule for the namespace/queue:
67
+
68
+
See the following topic that shows how to create an authorization rule for the namespace/queue:
139
69
[Create a Service Bus authorization rule for namespace and queue using an Azure Resource Manager template](service-bus-resource-manager-namespace-auth-rule.md)
140
70
141
71
Learn how to manage these resources by viewing these articles:
Copy file name to clipboardExpand all lines: articles/storage/common/storage-use-azcopy-v10.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -283,7 +283,7 @@ The URL appears in the output of this command. Your script can then download AzC
283
283
284
284
### Escape special characters in SAS tokens
285
285
286
-
In batch files that have the `.cmd` extension, you'll have to escape the `%` characters that appear in SAS tokens. You can do that by adding an addition`%` character next to existing `%` characters in the SAS token string.
286
+
In batch files that have the `.cmd` extension, you'll have to escape the `%` characters that appear in SAS tokens. You can do that by adding an additional`%` character next to existing `%` characters in the SAS token string.
0 commit comments