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/azure-functions/flex-consumption-plan.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -136,6 +136,8 @@ In Flex Consumption, many of the standard application settings and site configur
136
136
137
137
Keep these other considerations in mind when using Flex Consumption plan during the current preview:
138
138
139
+
+** Host ** There is a 30 seconds timeout for the app initialization. If your function app takes longer than 30 seconds to start you will see gRPC related System.TimeoutException entries. This will be configurable and a more clear exception will be implemented as part of [this host work item](https://github.com/Azure/azure-functions-host/issues/10482).
140
+
+** Durable Functions Performance ** Due to the per function scaling nature of Flex Consumption, to ensure the best performance for Durable Functions we recommend setting the [Always Ready instance count](./flex-consumption-how-to.md#set-always-ready-instance-counts) for the `durable` group to `1`. Also, with the Azure Storage provider, consider reducing the [queue polling interval](./durable/durable-functions-azure-storage-provider.md#queue-polling) to 10 seconds or less.
139
141
+**VNet Integration** Ensure that the `Microsoft.App` Azure resource provider is enabled for your subscription by [following these instructions](/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider). The subnet delegation required by Flex Consumption apps is `Microsoft.App/environments`.
140
142
+**Triggers**: All triggers are fully supported except for Kafka and Azure SQL triggers. The Blob storage trigger only supports the [Event Grid source](./functions-event-grid-blob-trigger.md). Non-C# function apps must use version `[4.0.0, 5.0.0)` of the [extension bundle](./functions-bindings-register.md#extension-bundles), or a later version.
Copy file name to clipboardExpand all lines: articles/azure-maps/rest-api-azure-maps.md
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ titleSuffix: Microsoft Azure Maps
4
4
description: Links to the Azure Maps Rest API.
5
5
author: sinnypan
6
6
ms.author: sipa
7
-
ms.date: 02/05/2024
7
+
ms.date: 09/23/2024
8
8
ms.topic: reference
9
9
ms.service: azure-maps
10
10
ms.subservice: rest-api
@@ -22,12 +22,12 @@ The most recent stable release of the Azure Maps services.
22
22
23
23
| API | API version | Description |
24
24
|-----|-------------|-------------|
25
-
|[Data Registry]| 2023-06-01 | Programmatically store and update geospatial data to use in spatial operations. |
25
+
|[Data Registry]| 2023-06-01 | Programmatically store and update geospatial data to use in spatial operations.<br>The Data registry service is deprecated and will be retired on 9/30/25.|
26
26
|[Geolocation]| 1.0 | Convert IP addresses to country/region ISO codes. |
27
27
|[Render]| 2024-04-01 | Get road, satellite/aerial, weather, traffic map tiles, and static map images. |
28
28
|[Route]| 1.0 | Calculate optimized travel times and distances between locations for multiple modes of transportation and get localized travel instructions. |
29
29
|[Search]| 2023-06-01 | Geocode addresses and coordinates, search for business listings and places by name or category and get administrative boundary polygons. |
30
-
|[Spatial]| 2022-08-01 | Use geofences, great circle distances and other spatial operations to analyze location data. |
30
+
|[Spatial]| 2022-08-01 | Use geofences, great circle distances and other spatial operations to analyze location data.<br>The Spatial service is deprecated and will be retired on 9/30/25.|
31
31
|[Timezone]| 1.0 | Get time zone and sunrise/sunset information for specified locations. |
32
32
|[Traffic]| 1.0 | Get current traffic information including traffic flow and traffic incident details. |
33
33
|[Weather]| 1.1 | Get current, forecasted, and historical weather conditions, air quality, tropical storm details and weather along a route. |
@@ -58,8 +58,6 @@ Prerelease version of an Azure Maps service. Preview releases contain new functi
58
58
|[Route][Route-2023-10-01-preview]| 2023-10-01-preview | Returns the ideal route in GeoJSON between locations for multiple modes of transportation.<BR><BR>Some of the updates in this version of the Route service include:<ul><li>Routes with "via" waypoints that the route must pass through.</li><li>More geographies</li><li>More languages available for localized travel instructions.</li></ul> |
59
59
60
60
<!--- Links to latest versions of each service ---------------------------------->
61
-
[Data]: /rest/api/maps/data
62
-
[How to create data registry]: /azure/azure-maps/how-to-create-data-registries
63
61
[Data Registry]: /rest/api/maps/data-registry
64
62
[Geolocation]: /rest/api/maps/geolocation
65
63
[Render]: /rest/api/maps/render
@@ -73,7 +71,6 @@ Prerelease version of an Azure Maps service. Preview releases contain new functi
73
71
<!--- Links to previous versions of each service -------------------------------->
Copy file name to clipboardExpand all lines: articles/azure-maps/rest-api-creator.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,14 +4,20 @@ titleSuffix: Microsoft Azure Maps Creator
4
4
description: Links to the Azure Maps Creator Rest API
5
5
author: faterceros
6
6
ms.author: aterceros
7
-
ms.date: 02/05/2024
7
+
ms.date: 09/23/2024
8
8
ms.topic: reference
9
9
ms.service: azure-maps
10
10
ms.subservice: creator
11
11
---
12
12
13
13
# Creator Rest API
14
14
15
+
> [!NOTE]
16
+
>
17
+
> **Azure Maps Creator retirement**
18
+
>
19
+
> The Azure Maps Creator indoor map service is now deprecated and will be retired on 9/30/25. For more information, see [End of Life Announcement of Azure Maps Creator](https://aka.ms/AzureMapsCreatorDeprecation).
20
+
15
21
Indoor mapping is a technology that enables the creation of digital maps of the interior of buildings. It helps visitors navigate through buildings and locate points of interest such as restrooms, conference rooms, and offices. Indoor mapping can be used to create a more convenient and enjoyable visitor experience. Visitors can spend less time searching for building directories and more time discovering new points of interest. With Azure Maps Creator, you can create indoor maps that enable customers to zoom in and out of a building to see each floor and navigate to any desired location using Creator's wayfinding service. In addition to common mapping functionality, Azure Maps Creator offers an array of useful services that enable you to implement functionality such as asset tracking, facility management, workspace optimization, hybrid work models to support a blend of in-office, remote, and on-the-go working, and much more.
16
22
17
23
The following tables offer high-level overviews of the services that Azure Maps Creator offers:
Copy file name to clipboardExpand all lines: articles/lab-services/retirement-guide.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -111,6 +111,17 @@ Partners might provide migration tooling to automatically migrate labs from Azur
111
111
- Dev Box requires specific Dev Box supported Marketplace images.
112
112
- AVD requires multi-session Marketplace images to enable multi-session capabilities.
113
113
114
+
### Can I transfer my Azure Lab Services core limits to my preferred transition solution?
115
+
No, your Azure subscription core limits can't be transferred to your preferred solution, applicable to both Lab Account (Classic) and Lab Plan. You or the partner have to request a core limit for your chosen solution as part of the transition plan.
116
+
117
+
To ensure that you have the resources you require when you need them, you should:
118
+
- Request capacity as far in advance as possible.
119
+
- Be flexible on the region where you're requesting capacity, if possible.
120
+
- Make incremental requests for VM cores rather than making large, bulk requests. Break requests for large number of cores into smaller requests for extra flexibility in how those requests are fulfilled.
121
+
122
+
### Should I request the same amount of Azure subscription core limits with my preferred transition solution?
123
+
Make sure to review your lab usage trends and not assume you require the same volume of core limits. Keep in mind, the recommended transition solutions allow for more efficient use of lab resources which can reduce the overall number of cores needed. For example, multi-session VDI offerings enable multiple users to share the same VM.
124
+
114
125
## Related content
115
126
116
127
-[Azure Lab Services to Azure DevTest Labs Transition Guide](/azure/lab-services/transition-devtest-labs-guidance)
0 commit comments