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/service-bus-messaging/includes/service-bus-create-topic-subscription-portal.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
@@ -1,6 +1,6 @@
1
1
---
2
-
title: include file
3
-
description: include file
2
+
title: Create an Azure Service Bus topic
3
+
description: Shows you how to create an Azure Service Bus topic in the Azure portal.
4
4
author: spelluru
5
5
ms.service: azure-service-bus
6
6
ms.topic: include
@@ -15,7 +15,7 @@
15
15
4. Enter a **name** for the topic. Leave the other options with their default values.
16
16
5. Select **Create**.
17
17
18
-
:::image type="content" source="./media/service-bus-create-topics-subscriptions-portal/create-topic.png" alt-text="Screenshot tthat shows the Create topic page in the Azure portal.":::
18
+
:::image type="content" source="./media/service-bus-create-topics-subscriptions-portal/create-topic.png" alt-text="Screenshot that shows the Create topic page in the Azure portal.":::
19
19
20
20
## Create a subscription to the topic
21
21
1. Select the **topic** that you created in the previous section.
Copy file name to clipboardExpand all lines: articles/service-bus-messaging/service-bus-faq.yml
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -105,12 +105,12 @@ sections:
105
105
3. Run nslookup for each one with suffixes s1, s2, and s3 to get the IP addresses of all three instances running in three availability zones,
106
106
107
107
> [!NOTE]
108
-
> The IP address returned by the `nslookup` command isn't a static IP address. It remains constant until the underlying deployment is deleted or moved to a different cluster, however using IN addresses is not recommended or supported, and you will need to keep track of changes to the IP addresses.
108
+
> The IP address returned by the `nslookup` command isn't a static IP address. It remains constant until the underlying deployment is deleted or moved to a different cluster, however using IN addresses isn't recommended or supported, and you'll need to keep track of changes to the IP addresses.
109
109
110
110
- question: |
111
111
Where can I find the IP address of the client sending/receiving messages to/from a namespace?
112
112
answer: |
113
-
We don't log the IP addresses of clients sending or receiving messages to/from your namespace. Regenerate keys so that all existing clients will fail to authenticate and review [Azure role-based access control (Azure RBAC)](authenticate-application.md#azure-built-in-roles-for-azure-service-bus)) settings to ensure that only allowed users or applications have access to the namespace.
113
+
We don't log the IP addresses of clients sending or receiving messages to/from your namespace. Regenerate keys so that all existing clients fail to authenticate and review [Azure role-based access control (Azure RBAC)](authenticate-application.md#azure-built-in-roles-for-azure-service-bus)) settings to ensure that only allowed users or applications have access to the namespace.
114
114
115
115
If you're using a **premium** namespace, use [IP filtering](service-bus-ip-filtering.md), [virtual network service endpoints](service-bus-service-endpoints.md), and [private endpoints](private-link-service.md) to limit access to the namespace.
116
116
@@ -142,12 +142,12 @@ sections:
142
142
- question: |
143
143
How do you charge for Service Bus?
144
144
answer: |
145
-
For complete information about Service Bus pricing, see [Service Bus pricing details](https://azure.microsoft.com/pricing/details/service-bus/). In addition to the prices noted, you are charged for associated data transfers for egress outside of the data center in which your application is provisioned.
145
+
For complete information about Service Bus pricing, see [Service Bus pricing details](https://azure.microsoft.com/pricing/details/service-bus/). In addition to the prices noted, you're charged for associated data transfers for egress outside of the data center in which your application is provisioned.
146
146
147
147
- question: |
148
148
What usage of Service Bus is subject to data transfer? What isn't?
149
149
answer: |
150
-
Any data transfer within a given Azure region is provided at no charge, as well as any inbound data transfer. Data transfer outside a region is subject to egress charges, which can be found [here](https://azure.microsoft.com/pricing/details/bandwidth/).
150
+
Any data transfer within a given Azure region is provided at no charge, and any inbound data transfer. Data transfer outside a region is subject to egress charges, which can be found [here](https://azure.microsoft.com/pricing/details/bandwidth/).
Copy file name to clipboardExpand all lines: articles/service-bus-messaging/service-bus-quotas.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
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Microsoft Azure Service Bus quotas and limits
3
-
description: This article lists basic quotas and throttling thresholds in Azure Service Bus messaging. For example - maximum number of namespaces per subscription.
3
+
description: This article lists basic quotas and throttling thresholds in Azure Service Bus messaging. For example, maximum number of namespaces per subscription.
0 commit comments