Merge pull request #292053 from pamistel/main

Removing all references to deprecated spatial-maps service

Author: Jill Grant

articles/azure-resource-manager/management/azure-services-resource-providers.md

@@ -136,7 +136,6 @@ The resource providers for developer tools services are:
 | Microsoft.DevCenter | [Microsoft Dev Box](../../dev-box/index.yml) |
 | Microsoft.DevSpaces | [Azure Dev Spaces](/previous-versions/azure/dev-spaces/) |
 | Microsoft.LoadTestService | [Azure Load Testing](/azure/load-testing/) |
-| Microsoft.MixedReality | [Azure Spatial Anchors](../../spatial-anchors/index.yml) |
 | Microsoft.Notebooks | [Azure Notebooks](https://notebooks.azure.com/help/introduction) |
 
 ## DevOps resource providers

articles/azure-resource-manager/management/move-support-resources.md

@@ -1298,7 +1298,6 @@ Moves between Resource groups and subscriptions are supported for APIs that use
 > | ------------- | ----------- | ---------- | ---------- |
 > | objectunderstandingaccounts | No | No | No |
 > | remoterenderingaccounts | **Yes** | **Yes** | No |
-> | spatialanchorsaccounts | **Yes** | **Yes** | No |
 
 ## Microsoft.MobileNetwork
 

articles/azure-resource-manager/management/tag-support.md

@@ -2202,7 +2202,6 @@ To get the same data as a file of comma-separated values, download [tag-support.
 > | objectAnchorsAccounts | Yes | Yes |
 > | objectUnderstandingAccounts | Yes | Yes |
 > | remoteRenderingAccounts | Yes | Yes |
-> | spatialAnchorsAccounts | Yes | Yes |
 
 ## Microsoft.MobileNetwork
 

articles/azure-resource-manager/templates/deployment-complete-mode-deletion.md

@@ -2202,7 +2202,6 @@ The resources are listed by resource provider namespace. To match a resource pro
 > | objectAnchorsAccounts | Yes |
 > | objectUnderstandingAccounts | Yes |
 > | remoteRenderingAccounts | Yes |
-> | spatialAnchorsAccounts | Yes |
 
 ## Microsoft.MobileNetwork
 

articles/governance/resource-graph/reference/supported-tables-resources.md

@@ -596,7 +596,6 @@ For sample queries for this table, see [Resource Graph sample queries for resour
 - Microsoft.MixedReality/objectAnchorsAccounts (Object Anchors Accounts)
 - Microsoft.MixedReality/objectUnderstandingAccounts (Object Understanding Accounts)
 - Microsoft.MixedReality/remoteRenderingAccounts (Remote Rendering Accounts)
-- Microsoft.MixedReality/spatialAnchorsAccounts (Spatial Anchors Accounts)
 - microsoft.mixedreality/surfacereconstructionaccounts
 - Microsoft.MobileNetwork/mobileNetworks (Mobile Networks)
 - microsoft.mobilenetwork/mobilenetworks/datanetworks

articles/index.yml

@@ -1151,14 +1151,6 @@ productDirectory:
         - mixed-reality
       url: object-anchors/index.yml
     # Card
-    - title: Spatial Anchors
-      summary: Create multi-user, spatially aware mixed reality experiences
-      imageSrc: ./media/index/spatial-anchor-accounts.svg
-      azureCategories:
-        - mixed-reality
-        - mobile
-      url: spatial-anchors/index.yml
-    # Card
     - title: Azure Remote Rendering
       summary: Render high-quality, interactive 3D content, and stream it to your devices in real time
       imageSrc: ./media/index/remote-rendering.svg

articles/media/index/spatial-anchor-accounts.svg

@@ -36,7 +36,7 @@ Azure has many native geospatial capabilities. In this diagram and the ones that
 
    :::image type="content" source="media/geospatial-overview.png" alt-text="Geospatial On Azure" lightbox="media/geospatial-overview.png":::
 
-This architecture flow assumes that the data may be coming from databases, files or streaming sources and not stored in a native GIS format. Once the data is ingested with Azure Data Factory, or via Azure IoT, Event Hubs and Stream Analytics, it could then be stored permanently in warm storage with Azure SQL, Azure SQL Managed Instance, Azure Database for PostgreSQL or Azure Data Lake Storage. From there, the data can be transformed and processed in batch with Azure Batch or Synapse Spark Pool, of which both can be automated through the usage of an Azure Data Factory or Synapse pipeline. For real-time data, it can be further transformed or processed with Stream Analytics, Azure Maps or brought into context with Azure Digital Twins. Once the data is transformed, it can then once again be served for additional uses in Azure SQL DB or Azure Database for PostgreSQL, Synapse SQL Pool (for abstracted non-geospatial data), Azure Cosmos DB, or Azure Data Explorer. Once ready, the data can be queried directly through the data base API, but frequently a publish layer is used. The Azure Maps Data API would suffice for small datasets, otherwise a non-native service can be introduced based on OSS or COTS, for accessing the data through web services or desktop applications. Finally, the Azure Maps Web SDK hosted in Azure App Service would allow for geovisualization. Another option is to use Azure Maps in Power BI. Lastly, HoloLens and Azure Spatial Anchors can be used to view the data and place it in the real-world for virtual reality (VR) and augmented reality (AR) experiences.
+This architecture flow assumes that the data may be coming from databases, files or streaming sources and not stored in a native GIS format. Once the data is ingested with Azure Data Factory, or via Azure IoT, Event Hubs and Stream Analytics, it could then be stored permanently in warm storage with Azure SQL, Azure SQL Managed Instance, Azure Database for PostgreSQL or Azure Data Lake Storage. From there, the data can be transformed and processed in batch with Azure Batch or Synapse Spark Pool, of which both can be automated through the usage of an Azure Data Factory or Synapse pipeline. For real-time data, it can be further transformed or processed with Stream Analytics, Azure Maps or brought into context with Azure Digital Twins. Once the data is transformed, it can then once again be served for additional uses in Azure SQL DB or Azure Database for PostgreSQL, Synapse SQL Pool (for abstracted non-geospatial data), Azure Cosmos DB, or Azure Data Explorer. Once ready, the data can be queried directly through the data base API, but frequently a publish layer is used. The Azure Maps Data API would suffice for small datasets, otherwise a non-native service can be introduced based on OSS or COTS, for accessing the data through web services or desktop applications. Finally, the Azure Maps Web SDK hosted in Azure App Service would allow for geovisualization. Another option is to use Azure Maps in Power BI.
 
 It should be noted as well that many of these options are optional and could be supplemented with OSS to reduce cost while also maintaining scalability, or 3rd party tools to utilize their specific capabilities. The next session addresses this need.
 

articles/orbital/geospatial-reference-architecture.md

@@ -98,7 +98,6 @@ As mentioned previously, Azure classifies services into three categories: founda
 > | Azure Red Hat OpenShift                              |
 > | Azure Remote Rendering                               |
 > | Azure SignalR Service                                |
-> | Azure Spatial Anchors                                |
 > | Azure Spring Apps                                    |
 > | Azure Storage: Archive Storage                       |
 > | Azure Synapse Analytics                              |