diff --git a/specification/maps/data-plane/Creator/preview/2.0/featurestate.json b/specification/maps/data-plane/Creator/preview/2.0/featurestate.json
index 4b31d74653e2..e586658567ba 100644
--- a/specification/maps/data-plane/Creator/preview/2.0/featurestate.json
+++ b/specification/maps/data-plane/Creator/preview/2.0/featurestate.json
@@ -173,7 +173,7 @@
},
"get": {
"summary": "Use to get a list of statesets.",
- "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\nSubmit List Statesets Request \n\nThe `List Statesets` API is an HTTP `GET` request used to return a list of existing statesets.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n### Submit List Statesets Request \n\nThe `List Statesets` API is an HTTP `GET` request used to return a list of existing statesets.",
"operationId": "FeatureState_ListStatesets",
"x-ms-examples": {
"List all the previously created statesets": {
@@ -208,7 +208,7 @@
"/featureStateSets/{statesetId}": {
"put": {
"summary": "Use to update the stateset style rules.",
- "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\nSubmit Update Stateset Request \n\nThe `Update Stateset` API is an HTTP `PUT` request used to update the stateset style rules of the specified stateset.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n### Submit Update Stateset Request \n\nThe `Update Stateset` API is an HTTP `PUT` request used to update the stateset style rules of the specified stateset.",
"operationId": "FeatureState_UpdateStateset",
"x-ms-examples": {
"Update stateset style rules with a statesetId": {
@@ -246,7 +246,7 @@
},
"delete": {
"summary": "Use to delete a stateset and its associated data.",
- "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\nSubmit Delete Request \n\nThe `Delete Stateset` API is an HTTP `DELETE` request used to delete the specified stateset and its associated data.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n### Submit Delete Stateset Request \n\nThe `Delete Stateset` API is an HTTP `DELETE` request used to delete the specified stateset and its associated data.",
"operationId": "FeatureState_DeleteStateset",
"x-ms-examples": {
"Delete an existing stateset": {
@@ -310,7 +310,7 @@
"put": {
"operationId": "FeatureState_UpdateStates",
"summary": "Use to update the state of a feature.",
- "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n Submit Update States Request \n\n The `Update States` API is a `PUT` request that allows the user to update the state of the specified feature in a given stateset.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n### Submit Update States Request \n\n The `Update States` API is a `PUT` request that allows the user to update the state of the specified feature in a given stateset.",
"x-ms-examples": {
"Update the states of a feature": {
"$ref": "./examples/featurestate/Featurestate_UpdateStates.json"
diff --git a/specification/maps/data-plane/Creator/preview/2.0/tileset.json b/specification/maps/data-plane/Creator/preview/2.0/tileset.json
index 24207bf8838c..85790fd25cdd 100644
--- a/specification/maps/data-plane/Creator/preview/2.0/tileset.json
+++ b/specification/maps/data-plane/Creator/preview/2.0/tileset.json
@@ -209,7 +209,7 @@
},
"delete": {
"summary": "Use to delete a tileset.",
- "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\nn### Submit Delete Request\n\nTo delete your content you will issue a `DELETE` request where the path will contain the `tilesetId` of the tileset to delete.
\n\n#### Delete request \"Successful\"\n\nThe Tileset Delete API returns a HTTP `204 No Content` response with an empty body, if the tileset was deleted successfully.
\n\n#### Delete request \"Failed\"\n\nA HTTP `400 Bad Request` error response will be returned if the tileset with the passed-in `tilesetId` is not found. \n\nHere is a sample error response:\n\n
\n\n```json\n{\n \"error\": {\n \"code\": \"400 BadRequest\",\n \"message\": \"Bad request - Tileset Id: d85b5b27-5fc4-4599-8b50-47160e90f8ce does not exist.\"\n }\n}\n```",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n### Submit Delete Request\n\nTo delete your content you will issue a `DELETE` request where the path will contain the `tilesetId` of the tileset to delete.\n\n#### Delete request \"Successful\"\n\nThe Tileset Delete API returns a HTTP `204 No Content` response with an empty body, if the tileset was deleted successfully.
\n\n#### Delete request \"Failed\"\n\nA HTTP `400 Bad Request` error response will be returned if the tileset with the passed-in `tilesetId` is not found. \n\nHere is a sample error response:\n\n
\n\n```json\n{\n \"error\": {\n \"code\": \"400 BadRequest\",\n \"message\": \"Bad request - Tileset Id: d85b5b27-5fc4-4599-8b50-47160e90f8ce does not exist.\"\n }\n}\n```",
"operationId": "Tileset_Delete",
"x-ms-examples": {
"Delete a created tileset": {
diff --git a/specification/maps/data-plane/Creator/preview/2023-03-01-preview/featurestate.json b/specification/maps/data-plane/Creator/preview/2023-03-01-preview/featurestate.json
index b98252308f14..2f83d4722344 100644
--- a/specification/maps/data-plane/Creator/preview/2023-03-01-preview/featurestate.json
+++ b/specification/maps/data-plane/Creator/preview/2023-03-01-preview/featurestate.json
@@ -128,7 +128,7 @@
"/featureStateSets": {
"post": {
"summary": "Use to create a new stateset.",
- "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator Feature State service retirement**\n>\n> The Azure Maps Creator [Feature State](/rest/api/maps-creator/feature-state) service is now deprecated and will be retired on 3/31/25. To avoid service disruptions, discontinue use of the Feature State services by 3/31/25. For information on real-time feature styling in Creator, see [Enhance your indoor maps with real-time map feature styling](https://techcommunity.microsoft.com/t5/azure-maps-blog/enhance-your-indoor-maps-with-real-time-map-feature-styling/ba-p/4048929).\n\nThe Feature State service allows the user to update the states of a feature and query them to be used in other services. The dynamic properties of a feature that don't belong to the dataset are referred to as *states* here.\n\nThis Feature State service pivot on the Stateset. Like Tileset, Stateset encapsulates the storage mechanism for feature states for a dataset.\n\nOnce the stateset is created, users can use that `statesetId` to post feature state updates and retrieve the current feature states. A feature can have only one state at a given point in time. \n\nFeature state is defined by the key name, value and the timestamp. When a feature state update is posted to Azure Maps, the state value gets updated only if the provided state's timestamp is later than the stored timestamp. \n\nAzure Maps MapControl provides a way to use these feature states to style the features. For more information, see the Render services [Get Map State Tile](/rest/api/maps/render/get-map-state-tile).\n\n### Submit Create Request\n\nThe `Create Stateset` API is an HTTP `POST` request used to create a new Stateset, defining the values and corresponding styles for its properties in the body of the request. For more information, see [Create a feature stateset](/azure/azure-maps/how-to-creator-feature-stateset).",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\nThe Feature State service allows the user to update the states of a feature and query them to be used in other services. The dynamic properties of a feature that don't belong to the dataset are referred to as *states* here.\n\nThis Feature State service pivot on the Stateset. Like Tileset, Stateset encapsulates the storage mechanism for feature states for a dataset.\n\nOnce the stateset is created, users can use that `statesetId` to post feature state updates and retrieve the current feature states. A feature can have only one state at a given point in time. \n\nFeature state is defined by the key name, value and the timestamp. When a feature state update is posted to Azure Maps, the state value gets updated only if the provided state's timestamp is later than the stored timestamp. \n\nAzure Maps MapControl provides a way to use these feature states to style the features. For more information, see the Render services [Get Map State Tile](/rest/api/maps/render/get-map-state-tile).\n\n### Submit Create Request\n\nThe `Create Stateset` API is an HTTP `POST` request used to create a new Stateset, defining the values and corresponding styles for its properties in the body of the request. For more information, see [Create a feature stateset](/azure/azure-maps/how-to-creator-feature-stateset).",
"operationId": "FeatureState_CreateStateset",
"x-ms-examples": {
"Create a new stateset with a datasetId": {
@@ -172,7 +172,7 @@
},
"get": {
"summary": "Use to get a list of statesets.",
- "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator Feature State service retirement**\n>\n> The Azure Maps Creator [Feature State](/rest/api/maps-creator/feature-state) service is now deprecated and will be retired on 3/31/25. To avoid service disruptions, discontinue use of the Feature State services by 3/31/25. For information on real-time feature styling in Creator, see [Enhance your indoor maps with real-time map feature styling](https://techcommunity.microsoft.com/t5/azure-maps-blog/enhance-your-indoor-maps-with-real-time-map-feature-styling/ba-p/4048929).\n\n ### Submit List Statesets Request \n\n The `List Statesets` API is an HTTP `GET` request that returns a list of all existing statesets.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n ### Submit List Statesets Request \n\n The `List Statesets` API is an HTTP `GET` request that returns a list of all existing statesets.",
"operationId": "FeatureState_ListStatesets",
"x-ms-examples": {
"List all the previously created statesets": {
@@ -207,7 +207,7 @@
"/featureStateSets/{statesetId}": {
"put": {
"summary": "Use to update the stateset style rules.",
- "description": "\n\n > [!NOTE]\n>\n> **Azure Maps Creator Feature State service retirement**\n>\n> The Azure Maps Creator [Feature State](/rest/api/maps-creator/feature-state) service is now deprecated and will be retired on 3/31/25. To avoid service disruptions, discontinue use of the Feature State services by 3/31/25. For information on real-time feature styling in Creator, see [Enhance your indoor maps with real-time map feature styling](https://techcommunity.microsoft.com/t5/azure-maps-blog/enhance-your-indoor-maps-with-real-time-map-feature-styling/ba-p/4048929).\n\n### Submit Update Stateset Request \n\nThe `Update Stateset` API is an HTTP `PUT` request used to update the stateset style rules of the specified stateset.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n### Submit Update Stateset Request \n\nThe `Update Stateset` API is an HTTP `PUT` request used to update the stateset style rules of the specified stateset.",
"operationId": "FeatureState_UpdateStateset",
"x-ms-examples": {
"Update stateset style rules with a statesetId": {
@@ -245,7 +245,7 @@
},
"delete": {
"summary": "Use to delete a stateset and its associated data.",
- "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator Feature State service retirement**\n>\n> The Azure Maps Creator [Feature State](/rest/api/maps-creator/feature-state) service is now deprecated and will be retired on 3/31/25. To avoid service disruptions, discontinue use of the Feature State services by 3/31/25. For information on real-time feature styling in Creator, see [Enhance your indoor maps with real-time map feature styling](https://techcommunity.microsoft.com/t5/azure-maps-blog/enhance-your-indoor-maps-with-real-time-map-feature-styling/ba-p/4048929).\n\n### Submit Delete Stateset Request\n\n The `Delete Stateset` API is an HTTP `DELETE` request used to delete the specified stateset and its associated data.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n### Submit Delete Stateset Request\n\n The `Delete Stateset` API is an HTTP `DELETE` request used to delete the specified stateset and its associated data.",
"operationId": "FeatureState_DeleteStateset",
"x-ms-examples": {
"Delete an existing stateset": {
@@ -274,7 +274,7 @@
},
"get": {
"summary": "Use to retrieve stateset information.",
- "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator Feature State service retirement**\n>\n> The Azure Maps Creator [Feature State](/rest/api/maps-creator/feature-state) service is now deprecated and will be retired on 3/31/25. To avoid service disruptions, discontinue use of the Feature State services by 3/31/25. For information on real-time feature styling in Creator, see [Enhance your indoor maps with real-time map feature styling](https://techcommunity.microsoft.com/t5/azure-maps-blog/enhance-your-indoor-maps-with-real-time-map-feature-styling/ba-p/4048929).\n\n### Submit Get Stateset Request\n\n The `Get Stateset` API is an HTTP `GET` request used to retrieve the specified stateset information, including the `datasetId` associated to the stateset, and its styles.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n### Submit Get Stateset Request\n\n The `Get Stateset` API is an HTTP `GET` request used to retrieve the specified stateset information, including the `datasetId` associated to the stateset, and its styles.",
"operationId": "FeatureState_GetStateset",
"x-ms-examples": {
"Get stateset information with a statesetId": {
@@ -308,7 +308,7 @@
"/featureStateSets/{statesetId}/featureStates/{featureId}": {
"put": {
"summary": "Use to update the state of a feature.",
- "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator Feature State service retirement**\n>\n> The Azure Maps Creator [Feature State](/rest/api/maps-creator/feature-state) service is now deprecated and will be retired on 3/31/25. To avoid service disruptions, discontinue use of the Feature State services by 3/31/25. For information on real-time feature styling in Creator, see [Enhance your indoor maps with real-time map feature styling](https://techcommunity.microsoft.com/t5/azure-maps-blog/enhance-your-indoor-maps-with-real-time-map-feature-styling/ba-p/4048929).\n\n ### Submit Update States Request \n\n The `Update States` API is a `PUT` request that allows the user to update the state of the specified feature in a given stateset.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n### Submit Update States Request \n\n The `Update States` API is a `PUT` request that allows the user to update the state of the specified feature in a given stateset.",
"operationId": "FeatureState_UpdateStates",
"x-ms-examples": {
"Update the states of a feature": {
@@ -350,7 +350,7 @@
"delete": {
"operationId": "FeatureState_DeleteState",
"summary": "Use to delete state information.",
- "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator Feature State service retirement**\n>\n> The Azure Maps Creator [Feature State](/rest/api/maps-creator/feature-state) service is now deprecated and will be retired on 3/31/25. To avoid service disruptions, discontinue use of the Feature State services by 3/31/25. For information on real-time feature styling in Creator, see [Enhance your indoor maps with real-time map feature styling](https://techcommunity.microsoft.com/t5/azure-maps-blog/enhance-your-indoor-maps-with-real-time-map-feature-styling/ba-p/4048929).\n\n ### Submit Delete State Request \n\n The `Delete State` API is an HTTP `DELETE` request is used to delete state information defined by the `stateKeyName` parameter for the specified feature as specified by the `featureId`.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n ### Submit Delete State Request \n\n The `Delete State` API is an HTTP `DELETE` request is used to delete state information defined by the `stateKeyName` parameter for the specified feature as specified by the `featureId`.",
"x-ms-examples": {
"Delete the given feature state": {
"$ref": "./examples/featurestate/Featurestate_DeleteFeatureState.json"
@@ -385,7 +385,7 @@
"get": {
"operationId": "FeatureState_ListStates",
"summary": "Use to get current state information.",
- "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator Feature State service retirement**\n>\n> The Azure Maps Creator [Feature State](/rest/api/maps-creator/feature-state) service is now deprecated and will be retired on 3/31/25. To avoid service disruptions, discontinue use of the Feature State services by 3/31/25. For information on real-time feature styling in Creator, see [Enhance your indoor maps with real-time map feature styling](https://techcommunity.microsoft.com/t5/azure-maps-blog/enhance-your-indoor-maps-with-real-time-map-feature-styling/ba-p/4048929).\n\n ### Submit List States Request \n\n The `List States` API is an HTTP `GET` request that returns the current state information associated with the given feature in the specified stateset.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n ### Submit List States Request \n\n The `List States` API is an HTTP `GET` request that returns the current state information associated with the given feature in the specified stateset.",
"x-ms-examples": {
"Get the current states of a feature": {
"$ref": "./examples/featurestate/Featurestate_ListStates.json"
diff --git a/specification/maps/data-plane/Creator/preview/2023-03-01-preview/routeset.json b/specification/maps/data-plane/Creator/preview/2023-03-01-preview/routeset.json
index 86e54b5611ad..f4c76599efec 100644
--- a/specification/maps/data-plane/Creator/preview/2023-03-01-preview/routeset.json
+++ b/specification/maps/data-plane/Creator/preview/2023-03-01-preview/routeset.json
@@ -186,7 +186,7 @@
"/routesets": {
"post": {
"summary": "Use to create a routeset.",
- "description": "\n\nThe `Create` API is an HTTP `POST` request that allows the caller to create a routeset from a dataset. The routeset is a data structure consumed by the Azure Maps [Wayfinding](/rest/api/maps-creator/wayfinding) service to discover the shortest paths within a facility.\n\nThe Create Routeset API is a [long-running operation](https://aka.ms/am-creator-lrt-v2).\n\nCreator makes it possible to develop applications based on your private indoor map data using Azure Maps API and SDKs. See the [Creator for indoor maps](https://docs.microsoft.com/azure/azure-maps/creator-indoor-maps) article for an introduction to the Azure Maps Creator concepts and tools.\n\n### Submit Create Request\n\nTo create a routeset, make a `POST` request with an empty body. The dataset is used as the source of the routeset data, so the `datasetId` query parameter must be included.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\nThe `Create` API is an HTTP `POST` request that allows the caller to create a routeset from a dataset. The routeset is a data structure consumed by the Azure Maps [Wayfinding](/rest/api/maps-creator/wayfinding) service to discover the shortest paths within a facility.\n\nThe Create Routeset API is a [long-running operation](https://aka.ms/am-creator-lrt-v2).\n\nCreator makes it possible to develop applications based on your private indoor map data using Azure Maps API and SDKs. See the [Creator for indoor maps](https://docs.microsoft.com/azure/azure-maps/creator-indoor-maps) article for an introduction to the Azure Maps Creator concepts and tools.\n\n### Submit Create Request\n\nTo create a routeset, make a `POST` request with an empty body. The dataset is used as the source of the routeset data, so the `datasetId` query parameter must be included.",
"operationId": "Routeset_Create",
"x-ms-long-running-operation": true,
"x-ms-long-running-operation-options": {
@@ -222,7 +222,7 @@
},
"get": {
"summary": "Use to get a list of routesets.",
- "description": "\n\nCreator makes it possible to develop applications based on your private indoor map data using Azure Maps API and SDKs. See the [Creator for indoor maps](https://docs.microsoft.com/azure/azure-maps/creator-indoor-maps) article for an introduction to the Azure Maps Creator concepts and tools.\n\n### Submit List Request\n\nThe `List` API is an HTTP `GET` request that allows the caller to fetch a list of all routesets in the current Azure Maps Creator account.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\nCreator makes it possible to develop applications based on your private indoor map data using Azure Maps API and SDKs. See the [Creator for indoor maps](https://docs.microsoft.com/azure/azure-maps/creator-indoor-maps) article for an introduction to the Azure Maps Creator concepts and tools.\n\n### Submit List Request\n\nThe `List` API is an HTTP `GET` request that allows the caller to fetch a list of all routesets in the current Azure Maps Creator account.",
"operationId": "Routeset_List",
"x-ms-examples": {
"Enumerate all routesets for a given subscription": {
@@ -257,7 +257,7 @@
"/routesets/{routesetId}": {
"get": {
"summary": "Use to get the details of a routeset.",
- "description": "\n\nCreator makes it possible to develop applications based on your private indoor map data using Azure Maps API and SDKs. See the [Creator for indoor maps](https://docs.microsoft.com/azure/azure-maps/creator-indoor-maps) article for an introduction to the Azure Maps Creator concepts and tools.\n\n### Submit Get Request\n\nThe `Get` API is an HTTP `GET` request that allows the caller to fetch the details of an existing routeset, specified by the `routesetId`.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\nCreator makes it possible to develop applications based on your private indoor map data using Azure Maps API and SDKs. See the [Creator for indoor maps](https://docs.microsoft.com/azure/azure-maps/creator-indoor-maps) article for an introduction to the Azure Maps Creator concepts and tools.\n\n### Submit Get Request\n\nThe `Get` API is an HTTP `GET` request that allows the caller to fetch the details of an existing routeset, specified by the `routesetId`.",
"operationId": "Routeset_Get",
"x-ms-examples": {
"Get details for a previously created dataset": {
@@ -289,7 +289,7 @@
},
"delete": {
"summary": "Use to delete a routeset.",
- "description": "\n\nCreator makes it possible to develop applications based on your private indoor map data using Azure Maps API and SDKs. See the [Creator for indoor maps](https://docs.microsoft.com/azure/azure-maps/creator-indoor-maps) article for an introduction to the Azure Maps Creator concepts and tools.\n\n### Submit Delete Request\n\nThe `Delete` API is an HTTP `DELETE` request sent with the `routesetId` of the routeset to delete.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\nCreator makes it possible to develop applications based on your private indoor map data using Azure Maps API and SDKs. See the [Creator for indoor maps](https://docs.microsoft.com/azure/azure-maps/creator-indoor-maps) article for an introduction to the Azure Maps Creator concepts and tools.\n\n### Submit Delete Request\n\nThe `Delete` API is an HTTP `DELETE` request sent with the `routesetId` of the routeset to delete.",
"operationId": "Routeset_Delete",
"x-ms-examples": {
"Delete an existing routeset": {
@@ -320,7 +320,7 @@
"/routesets/operations/{operationId}": {
"get": {
"summary": "Use to check the status of the routeset creation process.",
- "description": "\n\nThe `Get Operation` API is an HTTP `GET` request used to check the status of the routeset creation process and retrieve the `routesetId`.\n\n### Submit Operations Request\n\nTo view the current progress of a routeset operation, you will use a `GET` request where the `operationId` given the path is the ID that represents the operation.\n\n### Operation Response\n\nWhile in progress, a `200-OK` http status code is returned with no extra headers. If the operation succeeds, a `200-OK` http status code is returned with the `Resource-Location` in the header.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\nThe `Get Operation` API is an HTTP `GET` request used to check the status of the routeset creation process and retrieve the `routesetId`.\n\n### Submit Operations Request\n\nTo view the current progress of a routeset operation, you will use a `GET` request where the `operationId` given the path is the ID that represents the operation.\n\n### Operation Response\n\nWhile in progress, a `200-OK` http status code is returned with no extra headers. If the operation succeeds, a `200-OK` http status code is returned with the `Resource-Location` in the header.",
"operationId": "Routeset_GetOperation",
"x-ms-examples": {
"Get the status of an operation which is still running": {
diff --git a/specification/maps/data-plane/Creator/preview/2023-03-01-preview/style.json b/specification/maps/data-plane/Creator/preview/2023-03-01-preview/style.json
index f4008f605904..996d040c24fb 100644
--- a/specification/maps/data-plane/Creator/preview/2023-03-01-preview/style.json
+++ b/specification/maps/data-plane/Creator/preview/2023-03-01-preview/style.json
@@ -102,7 +102,7 @@
"/styles": {
"post": {
"summary": "Use to create an Azure Maps style.",
- "description": "\n\n## Submit Create Request\n\n The `Style Create` API is an HTTP `POST` request used to create an Azure Maps style by passing in either a JSON or ZIP file containing the style information. \n\nThe Create Style API is a [long-running operation](https://aka.ms/am-creator-lrt-v2).",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n### Submit Create Request\n\n The `Style Create` API is an HTTP `POST` request used to create an Azure Maps style by passing in either a JSON or ZIP file containing the style information. \n\nThe Create Style API is a [long-running operation](https://aka.ms/am-creator-lrt-v2).",
"operationId": "Style_Create",
"x-ms-long-running-operation": true,
"x-ms-long-running-operation-options": {
@@ -151,7 +151,7 @@
},
"get": {
"summary": "Use to get a list of styles.",
- "description": "\n\nThe `List` API is an HTTP `GET` request that allows the caller to fetch a list of all styles in the current Azure Maps Creator account. The default indoor style `microsoft-maps:indoor_2022-01-01` and `microsoft-maps:indoor_dark_2022-01-01` will not show in the list response. But you can still use it as your own style by the predefined alias.\n\n### Submit List Request",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\nThe `List` API is an HTTP `GET` request that allows the caller to fetch a list of all styles in the current Azure Maps Creator account. The default indoor style `microsoft-maps:indoor_2022-01-01` and `microsoft-maps:indoor_dark_2022-01-01` will not show in the list response. But you can still use it as your own style by the predefined alias.\n\n### Submit List Request",
"operationId": "Style_List",
"x-ms-examples": {
"Get a list of all styles": {
@@ -186,7 +186,7 @@
"/styles/{styleId}": {
"get": {
"summary": "Use to get details of a style.",
- "description": "\n\n### Submit Get Request\n\nThe `Get` API is an HTTP `GET` request that allows the caller to fetch the details of an existing style by passing in the `styleId` or its [alias](). Get the two predefined default styles using the alias `microsoft-maps:indoor_2022-01-01` for indoor light and `microsoft-maps:indoor_dark_2022-01-01` for indoor dark.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n### Submit Get Request\n\nThe `Get` API is an HTTP `GET` request that allows the caller to fetch the details of an existing style by passing in the `styleId` or its [alias](). Get the two predefined default styles using the alias `microsoft-maps:indoor_2022-01-01` for indoor light and `microsoft-maps:indoor_dark_2022-01-01` for indoor dark.",
"operationId": "Style_Get",
"x-ms-examples": {
"Get the details for a single style": {
@@ -229,7 +229,7 @@
},
"delete": {
"summary": "Use to delete a style.",
- "description": "\n\n### Submit Delete Request\n\n\n\nThe `Delete` API is an HTTP `DELETE` request that is used to delete the specified style, where the path will contain the `styleId` of the style to delete. \n\n#### Delete request \"Successful\"\n\nThe Style Delete API returns a HTTP `204 No Content` response with an empty body, if the style was deleted successfully. \n\n#### Delete request \"Failed\"\n\nA HTTP `400 Bad Request` error response will be returned if the style with the passed-in `styleId` is not found. \n\nHere is a sample error response:\n\n
\n\n```json\n{\n \"error\": {\n \"code\": \"400 BadRequest\",\n \"message\": \"Bad request - Style Id: d85b5b27-5fc4-4599-8b50-47160e90f8ce does not exist.\"\n }\n}\n```",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n### Submit Delete Request\n\n\n\nThe `Delete` API is an HTTP `DELETE` request that is used to delete the specified style, where the path will contain the `styleId` of the style to delete. \n\n#### Delete request \"Successful\"\n\nThe Style Delete API returns a HTTP `204 No Content` response with an empty body, if the style was deleted successfully. \n\n#### Delete request \"Failed\"\n\nA HTTP `400 Bad Request` error response will be returned if the style with the passed-in `styleId` is not found. \n\nHere is a sample error response:\n\n
\n\n```json\n{\n \"error\": {\n \"code\": \"400 BadRequest\",\n \"message\": \"Bad request - Style Id: d85b5b27-5fc4-4599-8b50-47160e90f8ce does not exist.\"\n }\n}\n```",
"operationId": "Style_Delete",
"x-ms-examples": {
"Delete a created style": {
@@ -260,7 +260,7 @@
"/styles/operations/{operationId}": {
"get": {
"summary": "Use to check the status of the style creation process.",
- "description": "\n\nThe `Get Operation` API is an HTTP `GET` request used to check the status of the style creation process and retrieve the `styletId`.\n\n### Submit Operations Request\n\nTo view the current progress of a style operation, you will use a `GET` request where the `operationId` given the path is the ID that represents the operation.\n\n### Operation Response\n\nWhile in progress, a `200-OK` http status code is returned with no extra headers. If the operation succeeds, a `200-OK` http status code is returned with the `Resource-Location` in the header.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\nThe `Get Operation` API is an HTTP `GET` request used to check the status of the style creation process and retrieve the `styletId`.\n\n### Submit Operations Request\n\nTo view the current progress of a style operation, you will use a `GET` request where the `operationId` given the path is the ID that represents the operation.\n\n### Operation Response\n\nWhile in progress, a `200-OK` http status code is returned with no extra headers. If the operation succeeds, a `200-OK` http status code is returned with the `Resource-Location` in the header.",
"operationId": "Style_GetOperation",
"x-ms-examples": {
"Get the status of an operation which is still running": {
diff --git a/specification/maps/data-plane/Creator/preview/2023-03-01-preview/tileset.json b/specification/maps/data-plane/Creator/preview/2023-03-01-preview/tileset.json
index 54bcf525868b..5bcd832d3cfa 100644
--- a/specification/maps/data-plane/Creator/preview/2023-03-01-preview/tileset.json
+++ b/specification/maps/data-plane/Creator/preview/2023-03-01-preview/tileset.json
@@ -102,7 +102,7 @@
"/tilesets": {
"post": {
"summary": "Use to create a tileset.",
- "description": "\n\n The `Create` API is an HTTP `POST` request used to create a tileset from the specified dataset. For more information, see [Create a tileset](/azure/azure-maps/tutorial-creator-indoor-maps#create-a-tileset). A tileset contains a set of tiles that can be consumed using [Get Map Tile](/rest/api/maps/render/get-map-tile) to retrieve custom tiles. To create a dataset, use [Dataset Create](/rest/api/maps-creator/dataset/create). For an introduction to concepts and tools that apply to Azure Maps Creator, see [Creator for indoor maps](/azure/azure-maps/creator-indoor-maps)..\n\n## Submit Create Request\n\nTo create your tileset you will make a `POST` request with an empty body. The `datasetId` query parameter will be used as the source of the tileset data.\n\nThe Create Tileset API is a [long-running operation](https://aka.ms/am-creator-lrt-v2).",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n The `Create` API is an HTTP `POST` request used to create a tileset from the specified dataset. For more information, see [Create a tileset](/azure/azure-maps/tutorial-creator-indoor-maps#create-a-tileset). A tileset contains a set of tiles that can be consumed using [Get Map Tile](/rest/api/maps/render/get-map-tile) to retrieve custom tiles. To create a dataset, use [Dataset Create](/rest/api/maps-creator/dataset/create). For an introduction to concepts and tools that apply to Azure Maps Creator, see [Creator for indoor maps](/azure/azure-maps/creator-indoor-maps)..\n\n## Submit Create Request\n\nTo create your tileset you will make a `POST` request with an empty body. The `datasetId` query parameter will be used as the source of the tileset data.\n\nThe Create Tileset API is a [long-running operation](https://aka.ms/am-creator-lrt-v2).",
"operationId": "Tileset_Create",
"x-ms-long-running-operation": true,
"x-ms-long-running-operation-options": {
@@ -147,7 +147,7 @@
},
"get": {
"summary": "Use to get a list of tilesets.",
- "description": "\n\n### Submit List Request\n\nThe `List` API is an HTTP `GET` request used to fetch a list of all existing tilesets.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n### Submit List Request\n\nThe `List` API is an HTTP `GET` request used to fetch a list of all existing tilesets.",
"operationId": "Tileset_List",
"x-ms-examples": {
"Get a list of all tilesets": {
@@ -182,7 +182,7 @@
"/tilesets/{tilesetId}": {
"get": {
"summary": "Use to get the details of a tileset.",
- "description": "\n\n### Submit Get Request\n\nThe `Get` API is an HTTP `GET` request used to fetch the details of a tileset.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n### Submit Get Request\n\nThe `Get` API is an HTTP `GET` request used to fetch the details of a tileset.",
"operationId": "Tileset_Get",
"x-ms-examples": {
"Gets the details for a single tileset": {
@@ -214,7 +214,7 @@
},
"delete": {
"summary": "Use to delete a tileset.",
- "description": "\n\n### Submit Delete Request\n\nThe `Delete` API is an HTTP `DELETE` request that is used to delete the specified tileset, where the path will contain the `tilesetId` of the tileset to delete.\n\n#### Delete request \"Successful\"\n\nThe Tileset Delete API returns a HTTP `204 No Content` response with an empty body, if the tileset was deleted successfully.
\n\n#### Delete request \"Failed\"\n\nA HTTP `400 Bad Request` error response will be returned if the tileset with the passed-in `tilesetId` is not found. \n\nHere is a sample error response:\n\n
\n\n```json\n{\n \"error\": {\n \"code\": \"400 BadRequest\",\n \"message\": \"Bad request - Tileset Id: d85b5b27-5fc4-4599-8b50-47160e90f8ce does not exist.\"\n }\n}\n```",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n### Submit Delete Request\n\nThe `Delete` API is an HTTP `DELETE` request that is used to delete the specified tileset, where the path will contain the `tilesetId` of the tileset to delete.\n\n#### Delete request \"Successful\"\n\nThe Tileset Delete API returns a HTTP `204 No Content` response with an empty body, if the tileset was deleted successfully.
\n\n#### Delete request \"Failed\"\n\nA HTTP `400 Bad Request` error response will be returned if the tileset with the passed-in `tilesetId` is not found. \n\nHere is a sample error response:\n\n
\n\n```json\n{\n \"error\": {\n \"code\": \"400 BadRequest\",\n \"message\": \"Bad request - Tileset Id: d85b5b27-5fc4-4599-8b50-47160e90f8ce does not exist.\"\n }\n}\n```",
"operationId": "Tileset_Delete",
"x-ms-examples": {
"Delete a created tileset": {
@@ -245,7 +245,7 @@
"/tilesets:fetchConfiguration": {
"get": {
"summary": "Use to get a tileset configuration.",
- "description": "\n\nThe Tileset `Get Configuration` request allows the caller to get a [tileset configuration](/rest/api/maps-creator/tileset/get-configuration#tilesetconfiguration) based on the dataset provided. The tileset configuration can then be used to create a custom tileset using [Tileset Create](/rest/api/maps-creator/tileset/create).\n\n Creator makes it possible to develop applications based on your private indoor map data using Azure Maps API and SDKs. For more information on concepts and tools that apply to Azure Maps Creator, see [Creator for indoor maps](/azure/azure-maps/creator-indoor-maps).\n\n### Submit Get Configuration Request\n\n The `Get Configuration` API is an HTTP `GET` request is used to get a tileset configuration based on the `datasetId.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\nThe Tileset `Get Configuration` request allows the caller to get a [tileset configuration](/rest/api/maps-creator/tileset/get-configuration#tilesetconfiguration) based on the dataset provided. The tileset configuration can then be used to create a custom tileset using [Tileset Create](/rest/api/maps-creator/tileset/create).\n\n Creator makes it possible to develop applications based on your private indoor map data using Azure Maps API and SDKs. For more information on concepts and tools that apply to Azure Maps Creator, see [Creator for indoor maps](/azure/azure-maps/creator-indoor-maps).\n\n### Submit Get Configuration Request\n\n The `Get Configuration` API is an HTTP `GET` request is used to get a tileset configuration based on the `datasetId.",
"operationId": "Tileset_GetConfiguration",
"x-ms-examples": {
"Gets the tileset configuration for a given dataset": {
@@ -279,7 +279,7 @@
"/tilesets:validateConfiguration": {
"post": {
"summary": "Use to validate a tileset configuration.",
- "description": "\n\n### Submit Validate Configuration Request\n\nThe `Validate Configuration` API is an HTTP `POST` request used to validate the specified [tileset configuration](/rest/api/maps-creator/tileset/validate-configuration#tilesetconfiguration) based on the provided `datasetId`.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\n### Submit Validate Configuration Request\n\nThe `Validate Configuration` API is an HTTP `POST` request used to validate the specified [tileset configuration](/rest/api/maps-creator/tileset/validate-configuration#tilesetconfiguration) based on the provided `datasetId`.",
"operationId": "Tileset_ValidateConfiguration",
"x-ms-examples": {
"Validates the correctness of a tileset configuration": {
@@ -322,7 +322,7 @@
"/tilesets/operations/{operationId}": {
"get": {
"summary": "Use to get the status of a tileset creation.",
- "description": "\n\nThe `Get Operation` API is an HTTP `GET` request is used to check the status of the tileset creation process and retrieve the `tilesetId` value. The path is obtained from a call to [Tileset - Create](/rest/api/maps-creator/tilesets/create). While in progress, an HTTP 200 is returned with no extra headers. Once successfully completed an HTTP 200 is returned with a `Resource-Location` header. For more information, see [Check the status of tileset creation](/azure/azure-maps/tutorial-creator-indoor-maps#check-the-status-of-tileset-creation).",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\nThe `Get Operation` API is an HTTP `GET` request is used to check the status of the tileset creation process and retrieve the `tilesetId` value. The path is obtained from a call to [Tileset - Create](/rest/api/maps-creator/tilesets/create). While in progress, an HTTP 200 is returned with no extra headers. Once successfully completed an HTTP 200 is returned with a `Resource-Location` header. For more information, see [Check the status of tileset creation](/azure/azure-maps/tutorial-creator-indoor-maps#check-the-status-of-tileset-creation).",
"operationId": "Tileset_GetOperation",
"x-ms-examples": {
"Get the status of an operation which is still running": {
diff --git a/specification/maps/data-plane/Creator/preview/2023-03-01-preview/wayfind.json b/specification/maps/data-plane/Creator/preview/2023-03-01-preview/wayfind.json
index 1a842dad5517..c8ffc0b7e7bf 100644
--- a/specification/maps/data-plane/Creator/preview/2023-03-01-preview/wayfind.json
+++ b/specification/maps/data-plane/Creator/preview/2023-03-01-preview/wayfind.json
@@ -260,7 +260,7 @@
"/wayfinding/path": {
"get": {
"summary": "Use to calculate the best path between two locations within a facility.",
- "description": "\n\n The Wayfinding Service is part of Creator, and adheres to the [Open Geospatial Consortium](http://docs.opengeospatial.org/is/17-069r3/17-069r3.html) standard. Wayfinding uses indoor map data from the [routeset](/rest/api/maps-creator/routeset) to calculate the best path between two locations within the same facility. For more information, see [Wayfinding](/azure/azure-maps/creator-indoor-maps#wayfinding-preview) in the _Creator for indoor maps_ concepts article.",
+ "description": "\n\n> [!NOTE]\n>\n> **Azure Maps Creator retirement**\n>\n> 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).\n\nThe Wayfinding Service is part of Creator, and adheres to the [Open Geospatial Consortium](http://docs.opengeospatial.org/is/17-069r3/17-069r3.html) standard. Wayfinding uses indoor map data from the [routeset](/rest/api/maps-creator/routeset) to calculate the best path between two locations within the same facility. For more information, see [Wayfinding](/azure/azure-maps/creator-indoor-maps#wayfinding-preview) in the _Creator for indoor maps_ concepts article.",
"operationId": "Wayfinding_GetPath",
"x-ms-examples": {
"Get the shortest path between two points in the facility.": {