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/api-management/api-management-get-started-publish-versions.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.author: danlep
12
12
---
13
13
# Tutorial: Publish multiple versions of your API
14
14
15
-
There are times when it's impractical to have all callers to your API use exactly the same version. When callers want to upgrade to a later version, they want an approach that's easy to understand. As shown in this tutorial, it is possible to provided multiple *versions* in Azure API Management.
15
+
There are times when it's impractical to have all callers to your API use exactly the same version. When callers want to upgrade to a later version, they want an approach that's easy to understand. As shown in this tutorial, it is possible to provide multiple *versions* in Azure API Management.
16
16
17
17
For background, see [Versions & revisions](https://azure.microsoft.com/blog/versions-revisions/).
18
18
@@ -67,11 +67,13 @@ After creating the version, it now appears underneath **Demo Conference API** in
67
67
68
68
69
69
70
-
You can now edit and configure **v1** as an API that is separate from **Original**. Changes to one version do not affect another.
71
-
72
70
> [!Note]
73
71
> If you add a version to a non-versioned API, an **Original** is also automatically created. This version responds on the default URL. Creating an Original version ensures that any existing callers are not broken by the process of adding a version. If you create a new API with versions enabled at the start, an Original isn't created.
74
72
73
+
## Edit a version
74
+
75
+
After adding the version, you can now edit and configure it as an API that is separate from an Original. Changes to one version do not affect another. For example, add or remove API operations, or edit the OpenAPI specification. For more information, see [Edit an API](edit-api.md).
76
+
75
77
## Add the version to a product
76
78
77
79
In order for callers to see the new version, it must be added to a *product*. If you didn't already add the version to a product, you can add it to a product at any time.
Use the API Management [Purge](/rest/api/apimanagement/current-ga/deleted-services/purge) operation, substituting `{subscriptionId}`, `{location}`, and `{serviceName}` with your Azure subscription, resource location, and API Management name:
117
+
Use the API Management [Purge](/rest/api/apimanagement/current-ga/deleted-services/purge) operation, substituting `{subscriptionId}`, `{location}`, and `{serviceName}` with your Azure subscription, resource location, and API Management name.
118
+
119
+
> [!NOTE]
120
+
> To purge a soft-deleted instance, you must have the following RBAC permissions at the subscription scope: Microsoft.ApiManagement/locations/deletedservices/delete, Microsoft.ApiManagement/deletedservices/read.
Copy file name to clipboardExpand all lines: articles/azure-fluid-relay/reference/service-limits.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
@@ -9,9 +9,9 @@ ms.topic: reference
9
9
ms.service: azure-fluid
10
10
---
11
11
12
-
# Azure Fluid Relay Limits
12
+
# Azure Fluid Relay limits
13
13
14
-
This article outlines known limitation of Azure Fluid Relay.
14
+
This article outlines known limitations of Azure Fluid Relay.
15
15
16
16
## Distributed Data Structures
17
17
@@ -21,7 +21,7 @@ The Azure Fluid Relay doesn't support [experimental distributed data structures
21
21
22
22
The maximum number of simultaneous users in one session on Azure Fluid Relay is 100 users. This limit is on simultaneous users. What this means is that the 101st user won't be allowed to join the session. In the case where an existing user leaves the session, a new user will be able to join. This is because the number of simultaneous users at that point will be less than the limit.
23
23
24
-
## Fluid Summaries
24
+
## Fluid summaries
25
25
26
26
Incremental summaries uploaded to Azure Fluid Relay can't exceed 28 MB in size. More info [here](https://fluidframework.com/docs/concepts/summarizer).
Copy file name to clipboardExpand all lines: articles/azure-fluid-relay/resources/support.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
@@ -9,15 +9,15 @@ ms.topic: reference
9
9
ms.service: azure-fluid
10
10
---
11
11
12
-
# Help and Support options for Azure Fluid Relay
12
+
# Help and support options for Azure Fluid Relay
13
13
14
14
If you have an issue or question involving Azure Fluid Relay, the following options are available.
15
15
16
-
## Check out Frequently Asked Questions
16
+
## Check out frequently asked questions
17
17
18
18
You can see if your question is already answered on our Frequently Asked Questions [page](faq.md).
19
19
20
-
## Create an Azure Support Request
20
+
## Create an Azure support request
21
21
22
22
With Azure, there are many [support options and plans](https://azure.microsoft.com/support/plans/) available, which you can explore and review. You can create a support ticket in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview).
Copy file name to clipboardExpand all lines: articles/connectors/built-in.md
+58-34Lines changed: 58 additions & 34 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: Overview about built-in connectors in Azure Logic Apps
3
-
description: Learn about built-in connectors that run natively to create automated integration workflows in Azure Logic Apps.
2
+
title: Built-in connector overview
3
+
description: Learn about built-in connectors that run natively in Azure Logic Apps.
4
4
services: logic-apps
5
5
ms.suite: integration
6
6
ms.reviewer: estfan, azla
@@ -24,22 +24,46 @@ This article provides a general overview about built-in connectors in Consumptio
24
24
25
25
## Built-in connectors in Consumption versus Standard
26
26
27
-
The following table lists the current and expanding galleries of built-in connectors available for Consumption versus Standard logic app workflows. An asterisk (**\***) marks [service provider-based built-in connectors](../logic-apps/custom-connector-overview.md#service-provider-interface-implementation).
27
+
The following table lists the current and expanding galleries of built-in connectors available for Consumption versus Standard logic app workflows. For Standard workflows, an asterisk (**\***) marks [built-in connectors based on the *service provider* model](#service-provider-interface-implementation), which is described in more detail later.
In Standard logic app workflows, a built-in connector that has the following attributes is informally known as a *service provider*:
39
+
40
+
* Is based on the [Azure Functions extensibility model](../azure-functions/functions-bindings-register.md).
41
+
42
+
* Provides access from a Standard logic app workflow to a service, such as Azure Blob Storage, Azure Service Bus, Azure Event Hubs, SFTP, and SQL Server.
43
+
44
+
Some built-in connectors support only a single way to authenticate a connection to the underlying service. Other built-in connectors can offer a choice, such as using a connection string, Azure Active Directory (Azure AD), or a managed identity.
45
+
46
+
* Runs in the same process as the redesigned Azure Logic Apps runtime.
47
+
48
+
These service provider-based built-in connectors are available alongside their [managed connector versions](managed.md).
49
+
50
+
In contrast, a built-in connector that's *not a service provider* has the following attributes:
51
+
52
+
* Isn't based on the Azure Functions extensibility model.
53
+
54
+
* Is directly implemented as a job within the Azure Logic Apps runtime, such as Schedule, HTTP, Request, and XML operations.
55
+
34
56
<aname="custom-built-in"></a>
35
57
36
58
## Custom built-in connectors
37
59
38
-
For Standard logic apps, if a built-connector isn't available for your scenario, you can create your own built-in connector. You can use the same [*service provider interface implementation*](../logic-apps/custom-connector-overview.md#service-provider-interface-implementation) that's used by service provider-based built-in connectors, such as SQL Server, Service Bus, Blob Storage, Event Hubs, and Blob Storage. This interface implementation is based on the [Azure Functions extensibility model](../azure-functions/functions-bindings-register.md) and provides the capability for you to create custom built-in connectors that anyone can use in Standard logic apps.
60
+
For Standard logic apps, you can create your own built-in connector with the same [built-in connector extensibility model](../logic-apps/custom-connector-overview.md#built-in-connector-extensibility-model) that's used by service provider-based built-in connectors, such as Azure Blob, Azure Event Hubs, Azure Service Bus, SQL Server, and more. This interface implementation is based on the [Azure Functions extensibility model](../azure-functions/functions-bindings-register.md) and provides the capability for you to create custom built-in connectors that anyone can use in Standard logic apps.
61
+
62
+
For Consumption logic apps, you can't create your own built-in connectors, but you create your own managed connectors.
39
63
40
64
For more information, review the following documentation:
41
65
42
-
*[Custom connectors for Standard logic apps](../logic-apps/custom-connector-overview.md#custom-connector-standard)
66
+
*[Custom connectors in Azure Logic Apps](../logic-apps/custom-connector-overview.md#custom-connector-standard)
43
67
*[Create custom built-in connectors for Standard logic apps](../logic-apps/create-custom-built-in-connector-standard.md)
44
68
45
69
<aname="general-built-in"></a>
@@ -120,19 +144,19 @@ You can use the following built-in connectors to perform general tasks, for exam
120
144
:::row-end:::
121
145
:::row:::
122
146
:::column:::
123
-
[![FTP icon][ftp-icon]][ftp-doc]
147
+
![FTP icon][ftp-icon]
124
148
\
125
149
\
126
-
[**FTP**][ftp-doc]<br>(*Standard logic app only*)
150
+
**FTP**<br>(*Standard logic app only*)
127
151
\
128
152
\
129
153
Connect to FTP or FTPS servers you can access from the internet so that you can work with your files and folders.
Connect to SFTP servers that you can access from the internet by using SSH so that you can work with your files and folders.
@@ -145,9 +169,9 @@ You can use the following built-in connectors to perform general tasks, for exam
145
169
146
170
<aname="service-built-in"></a>
147
171
148
-
## Service-based built-in connectors
172
+
## Built-in connectors for specific services and systems
149
173
150
-
Connectors for some services provide both built-in connectors and managed connectors, which might differ across these versions.
174
+
You can use the following built-in connectors to access specific services and systems. In Standard logic app workflows, some of these built-in connectors are also informally known as *service providers*, which can differ from their managed connector counterparts in some ways.
151
175
152
176
:::row:::
153
177
:::column:::
@@ -172,75 +196,75 @@ Connectors for some services provide both built-in connectors and managed connec
172
196
When Swagger is included, the triggers and actions defined by these apps appear like any other first-class triggers and actions in Azure Logic Apps.
Call [Azure-hosted functions](../azure-functions/functions-overview.md) to run your own *code snippets* (C# or Node.js) within your workflow.
223
+
Consume and publish events through an event hub. For example, get output from your logic app with Event Hubs, and then send that output to a real-time analytics provider.
Consume and publish events through an event hub. For example, get output from your logic app with Event Hubs, and then send that output to a real-time analytics provider.
261
+
Connect to your Azure Storage account so that you can create, update, query, and manage tables.
0 commit comments