Merge pull request #262347 from MicrosoftDocs/main

1/4 11:00 AM IST Publishing

Author: Saisang

articles/aks/kubelogin-authentication.md

@@ -19,7 +19,7 @@ This article provides an overview of the following authentication methods and ex
 * Interactive web browser
 * Service principal
 * Managed identity
-* Workflow identity
+* Workload identity
 
 ## Limitations
 
@@ -328,4 +328,4 @@ The AKS Microsoft Entra ID client application ID used by kubelogin to perform pu
 
 <!-- LINKS - external -->
 [client-go-cred-plugin]: https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins
-[oidc-federation-github]: https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure
+[oidc-federation-github]: https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure

articles/automation/troubleshoot/extension-based-hybrid-runbook-worker.md

@@ -2,7 +2,7 @@
 title: Troubleshoot extension-based Hybrid Runbook Worker issues in Azure Automation 
 description: This article tells how to troubleshoot and resolve issues that arise with Azure Automation extension-based Hybrid Runbook Workers.
 services: automation
-ms.date: 09/06/2023
+ms.date: 01/03/2024
 ms.topic: troubleshooting 
 ms.custom:
 ---
@@ -25,7 +25,7 @@ To help troubleshoot issues with extension-based Hybrid Runbook Workers:
 
 - Check the error message shown in the Hybrid worker extension status/Detailed Status. It contains error message(s) and respective recommendation(s) to fix the issue.
 
-- Run the troubleshooter tool on the VM and it will generate an output file. Open the output file and verify the errors identified by the troubleshooter tool.
+- Run the troubleshooter tool on the VM and it generates an output file. Open the output file and verify the errors identified by the troubleshooter tool.
   - For windows: you can find the troubleshooter at `C:\Packages\Plugins\Microsoft.Azure.Automation.HybridWorker.HybridWorkerForWindows\<version>\bin\troubleshooter\TroubleShootWindowsExtension.ps1`
   - For Linux: you can find the troubleshooter at `/var/lib/waagent/Microsoft.Azure.Automation.HybridWorker.HybridWorkerForLinux-<version>/Troubleshooter/LinuxTroubleshooter.py`
 
@@ -51,7 +51,7 @@ The Hybrid Runbook Worker jobs failed as it was unable to import Az modules.
 
 As a workaround, you can follow these steps:
 
-1. Go to the folder : C:\Program Files\Microsoft Monitoring Agent\Agent\AzureAutomation\7.3.1722.0\HybridAgent
+1. Go to the folder: C:\Program Files\Microsoft Monitoring Agent\Agent\AzureAutomation\7.3.1722.0\HybridAgent
 1. Edit the file with the name *Orchestrator.Sandbox.exe.config*
 1. Add the following lines inside the `<assemblyBinding>` tags:
 ```xml
@@ -61,12 +61,30 @@ As a workaround, you can follow these steps:
 </dependentAssembly>
 ```
 
-### Scenario: Job failed to start as the Hybrid Worker was not available when the scheduled job started
+### Scenario: Runbooks go into a suspended state on a Hybrid Runbook Worker when using a custom account on a server with User Account Control (UAC) enabled
+
+#### Issue
+Jobs fail and go into a suspended state on the Hybrid Runbook Worker. The Microsoft-SMA event logs indicate
+`Win32 Process Exited with code [2148734720]` and a corresponding error in Application log when the runbook tries to execute is `.NET Runtime version : 4.0.30319.0` indicating that the application couldn't be started.
+
+#### Cause
+When a system has UAC/LUA in place, permissions must be granted directly and not through any group membership and when user has to elevate permissions, the jobs begin to fail.
+
+#### Resolution
+For Custom user on the Hybrid Runbook Worker, update the permissions in the following folders:
+
+| Folder |Permissions |
+|--- | --- |
+| C:\ProgramData\AzureConnectedMachineAgent\Tokens | Read |
+| C:\Packages\Plugins\Microsoft.Azure.Automation.HybridWorker.HybridWorkerForWindows | Read and Execute |
+
+
+### Scenario: Job failed to start as the Hybrid Worker wasn't available when the scheduled job started
 
 #### Issue
 Job fails to start on a Hybrid Worker and you see the following error:
 
-*Failed to start, as hybrid worker was not available when scheduled job started, the hybrid worker was last active at mm/dd/yyyy*.
+*Failed to start, as hybrid worker wasn't available when scheduled job started, the hybrid worker was last active at mm/dd/yyyy*.
 
 #### Cause
 This error can occur due to the following reasons:
@@ -89,7 +107,7 @@ Job gets suspended with the following error message:
 #### Cause
 Jobs might get suspended due to any of the following reasons:
 - Each active Hybrid Worker in the group will poll for jobs every 30 seconds to see if any jobs are available. The Worker picks jobs on a first-come, first-serve basis. Depending on when a job was pushed, whichever Hybrid Worker within the Hybrid Worker Group pings the Automation service first picks up the job. A single hybrid worker can generally pick up four jobs per ping (that is, every 30 seconds). If your rate of pushing jobs is higher than four per 30 seconds and no other Worker picks up the job, the job might get suspended. 
-- Hybrid Worker might not be polling as expected every 30 seconds. This could happen if the Worker is not healthy or there are network issues.  
+- Hybrid Worker might not be polling as expected every 30 seconds. This could happen if the Worker isn't healthy or there are network issues.  
 
 #### Resolution
 - If the job limit for a Hybrid Worker exceeds four jobs per 30 seconds, you can add more Hybrid Workers to the Hybrid Worker group for high availability and load balancing. You can also schedule jobs so they do not exceed the limit of four jobs per 30 seconds. The processing time of the jobs queue depends on the Hybrid worker hardware profile and load. Ensure that the Hybrid Worker is healthy and gives a heartbeat. 
@@ -139,14 +157,14 @@ for Arc-enabled servers or [Manage VMware virtual machines Azure Arc](../../azur
 You are deploying an extension-based Hybrid Runbook Worker on a VM, and it fails with error: *Invalid Authorization Token*.
 
 ### Cause
-User-assigned managed identity of the VM is enabled, but system-assigned managed identity is not enabled. 
+User-assigned managed identity of the VM is enabled, but system-assigned managed identity isn't enabled. 
 
 ### Resolution
 Follow the steps listed below:
 
 1. [Enable](../../active-directory/managed-identities-azure-resources/qs-configure-portal-windows-vm.md#enable-system-assigned-managed-identity-on-an-existing-vm) System-assigned managed identity of the VM. 
 2. [Delete](../extension-based-hybrid-runbook-worker-install.md#delete-a-hybrid-runbook-worker) the Hybrid Worker extension installed on the VM. 
-3. Re-install the Hybrid Worker extension on the VM. 
+3. Reinstall the Hybrid Worker extension on the VM. 
 
 
 ### Scenario: Installation process of Hybrid Worker extension on Windows VM gets stuck

articles/azure-maps/about-creator.md

@@ -59,7 +59,6 @@ This section provides a high-level overview of the indoor map creation workflow.
 1. **Upload**. Upload your drawing packages into your Azure Storage
     account. For more information, see [How to create data registry].
 
-1. **Convert**. Once the drawing package is uploaded into your Azure Storage account,
 1. **Convert**. Once the drawing package is uploaded into your Azure Storage account,
     use the [Conversion] service to validate the data in the uploaded drawing
     package and convert it into map data.
@@ -111,7 +110,7 @@ This section provides a high-level overview of the indoor map creation workflow.
 
 [Azure Maps Creator onboarding tool]: https://azure.github.io/azure-maps-creator-onboarding-tool
 [Azure Maps Creator REST API]: /rest/api/maps-creator
-[Conversion]: /rest/api/maps/v2/conversion
+[Conversion]: /rest/api/maps-creator/conversion
 [Create a feature stateset]: how-to-creator-feature-stateset.md
 [Create custom styles for indoor maps]: how-to-create-custom-styles.md
 [Create dataset using GeoJson package]: how-to-dataset-geojson.md
@@ -124,7 +123,7 @@ This section provides a high-level overview of the indoor map creation workflow.
 [Dynamic maps StylesObject]: schema-stateset-stylesobject.md
 [Edit indoor maps using the QGIS plugin]: creator-qgis-plugin.md
 [Facility Ontology]: creator-facility-ontology.md
-[Features API]: /rest/api/maps/2023-03-01-preview/features
+[Features API]: /rest/api/maps-creator/features?view=rest-maps-creator-2023-03-01-preview
 [features]: glossary.md#feature
 [How to create data registry]: how-to-create-data-registries.md
 [Implement Dynamic styling for indoor maps]: indoor-map-dynamic-styling.md
@@ -136,12 +135,12 @@ This section provides a high-level overview of the indoor map creation workflow.
 [manifest]: drawing-requirements.md#manifest-file-requirements
 [onboarding tool]: https://azure.github.io/azure-maps-creator-onboarding-tool
 [Query datasets with WFS API]: how-to-creator-wfs.md
-[Routeset]: /rest/api/maps/2023-03-01-preview/routeset/create
+[Routeset]: /rest/api/maps-creator/routeset/create?view=rest-maps-creator-2023-03-01-preview
 [tileset]: creator-indoor-maps.md#tilesets
 [Tilesets]: creator-indoor-maps.md#tilesets
 [Use Azure Maps Creator to create indoor maps]: tutorial-creator-indoor-maps.md
 [Use the Azure Maps Indoor Maps module]: how-to-use-indoor-module.md
 [visual style editor]: https://azure.github.io/Azure-Maps-Style-Editor
-[Wayfinding service]: /rest/api/maps/2023-03-01-preview/wayfinding
+[Wayfinding service]: /rest/api/maps-creator/wayfinding?view=rest-maps-creator-2023-03-01-preview
 [Wayfinding]: creator-indoor-maps.md#wayfinding-preview
 [Work with datasets using the QGIS plugin]: creator-qgis-plugin.md

articles/azure-maps/creator-facility-ontology.md

@@ -575,12 +575,13 @@ Learn more about Creator for indoor maps by reading:
 [level.Id]: #level
 [structures]: #structure
 <!---------   REST API Links     --------------->
-[conversion service]: /rest/api/maps/v2/conversion
-[dataset]: /rest/api/maps/2023-03-01-preview/dataset
-[GeoJSON Point geometry]: /rest/api/maps/v2/wfs/get-features#geojsonpoint
-[MultiPolygon]: /rest/api/maps/v2/wfs/get-features?tabs=HTTP#geojsonmultipolygon
-[Point]: /rest/api/maps/v2/wfs/get-features#geojsonpoint
-[Polygon]: /rest/api/maps/v2/wfs/get-features?tabs=HTTP#geojsonpolygon
+[conversion service]: /rest/api/maps-creator/conversion
+[dataset]: /rest/api/maps-creator/dataset?view=rest-maps-creator-2023-03-01-preview
+[GeoJSON Point geometry]: /rest/api/maps-creator/wfs/get-features#geojsonpoint
+[MultiPolygon]: /rest/api/maps-creator/wfs/get-features?tabs=HTTP#geojsonmultipolygon
+[Point]: /rest/api/maps-creator/wfs/get-features#geojsonpoint
+[Polygon]: /rest/api/maps-creator/wfs/get-features?tabs=HTTP#geojsonpolygon
+
 <!---------   learn.microsoft.com links     --------------->
 [Create a dataset using a GeoJson package]: how-to-dataset-geojson.md
 [Creator for indoor maps]: creator-indoor-maps.md

articles/azure-maps/creator-indoor-maps.md

@@ -314,26 +314,26 @@ The following example shows how to update a dataset, create a new tileset, and d
 [Upload a drawing package]: #upload-a-drawing-package
 
 <!-----	REST API Links	------->
-[Alias API]: /rest/api/maps/v2/alias
-[Conversion service]: /rest/api/maps/v2/conversion
-[Creator - map configuration Rest API]: /rest/api/maps/2023-03-01-preview/map-configuration
-[Dataset Create]: /rest/api/maps/v2/dataset/create
-[Dataset service]: /rest/api/maps/v2/dataset
-[Feature State service]: /rest/api/maps/v2/feature-state
-[Feature State Update API]: /rest/api/maps/v2/feature-state/update-states
+[Creator - map configuration Rest API]: /rest/api/maps-creator/map-configuration?view=rest-maps-creator-2023-03-01-preview
+[routeset]: /rest/api/maps-creator/routeset?view=rest-maps-creator-2023-03-01-preview
+[Style - Create]: /rest/api/maps-creator/style/create?view=rest-maps-creator-2023-03-01-preview
+[style]: /rest/api/maps-creator/style?view=rest-maps-creator-2023-03-01-preview
+[tileset]: /rest/api/maps-creator/tileset?view=rest-maps-creator-2023-03-01-preview
+[wayfinding path]: /rest/api/maps-creator/wayfinding/get-path?view=rest-maps-creator-2023-03-01-preview
+[wayfinding service]: /rest/api/maps-creator/wayfinding?view=rest-maps-creator-2023-03-01-preview
+[wayfinding]: /rest/api/maps-creator/wayfinding?view=rest-maps-creator-2023-03-01-preview
+[Alias API]: /rest/api/maps-creator/alias
+[Conversion service]: /rest/api/maps-creator/conversion
+[Dataset Create]: /rest/api/maps-creator/dataset/create
+[Dataset service]: /rest/api/maps-creator/dataset
+[Feature State service]: /rest/api/maps-creator/feature-state
+[Feature State Update API]: /rest/api/maps-creator/feature-state/update-states
 [Geofence service]: /rest/api/maps/spatial/postgeofence
-[Render - Get Map Tile]: /rest/api/maps/render-v2/get-map-tile
-[routeset]: /rest/api/maps/2023-03-01-preview/routeset
-[Style - Create]: /rest/api/maps/2023-03-01-preview/style/create
-[style]: /rest/api/maps/2023-03-01-preview/style
-[Tileset Create]: /rest/api/maps/v2/tileset/create
-[Tileset List]: /rest/api/maps/v2/tileset/list
-[Tileset service]: /rest/api/maps/v2/tileset
-[tileset]: /rest/api/maps/2023-03-01-preview/tileset
-[wayfinding path]: /rest/api/maps/2023-03-01-preview/wayfinding/get-path
-[wayfinding service]: /rest/api/maps/2023-03-01-preview/wayfinding
-[wayfinding]: /rest/api/maps/2023-03-01-preview/wayfinding
-[Web Feature service]: /rest/api/maps/v2/wfs
+[Tileset Create]: /rest/api/maps-creator/tileset/create
+[Tileset List]: /rest/api/maps-creator/tileset/list
+[Tileset service]: /rest/api/maps-creator/tileset
+[Web Feature service]: /rest/api/maps-creator/wfs
+
 
 <!--- learn.microsoft.com Links ------------>
 [Authorization with role-based access control]: azure-maps-authentication.md#authorization-with-role-based-access-control

articles/azure-maps/creator-onboarding-tool.md

@@ -75,7 +75,7 @@ Integrate the indoor map into your applications using the Web SDK.
 > [Use the Azure Maps Indoor Maps module]
 
 [Azure Maps Creator onboarding tool]: https://azure.github.io/azure-maps-creator-onboarding-tool
-[Conversion service]: /rest/api/maps/v2/conversion
+[Conversion service]: /rest/api/maps-creator/conversion
 [Convert a drawing package]: creator-indoor-maps.md#convert-a-drawing-package
 [dataset]: creator-indoor-maps.md#datasets
 [Drawing package requirements]: drawing-requirements.md?pivots=drawing-package-v2

articles/azure-maps/creator-qgis-plugin.md

@@ -200,7 +200,7 @@ If you have question related to Azure Maps, see [MICROSOFT Q&A]. Be sure and tag
 [Download QGIS]: https://qgis.org/en/site/forusers/download.html
 [geographic information system (GIS)]: https://www.usgs.gov/faqs/what-geographic-information-system-gis
 [Installing New Plugins]: https://docs.qgis.org/3.28/en/docs/training_manual/qgis_plugins/fetching_plugins.html#basic-fa-installing-new-plugins
-[layer definition]: /rest/api/maps/2023-03-01-preview/features/get-collection-definition?tabs=HTTP
+[layer definition]: /rest/api/maps-creator/features/get-collection-definition?view=rest-maps-creator-2023-03-01-preview?tabs=HTTP
 [MICROSOFT Q&A]: /answers/questions/ask
 [QGIS]: https://qgis.org/en/site/
 [subscription key]: quick-demo-map-app.md#get-the-subscription-key-for-your-account

articles/azure-maps/drawing-conversion-error-codes.md

@@ -507,7 +507,7 @@ To fix a **verticalPenetrationError** error, read about how to use a vertical pe
 > [!div class="nextstepaction"]
 > [Creator for indoor mapping]
 
-[Conversion service]: /rest/api/maps/v2/conversion
+[Conversion service]: /rest/api/maps-creator/conversion
 [Creator for indoor mapping]: creator-indoor-maps.md
 [Drawing files requirements]: drawing-requirements.md#drawing-package-requirements
 [Drawing Package Guide]: drawing-package-guide.md

articles/azure-maps/drawing-error-visualizer.md

@@ -95,7 +95,7 @@ Learn more by reading:
 > [Creator for indoor maps]
 
 [Azure Maps account]: quick-demo-map-app.md#create-an-azure-maps-account
-[Azure Maps Conversion API]: /rest/api/maps/v2/conversion
+[Azure Maps Conversion API]: /rest/api/maps-creator/conversion
 [Convert a drawing package]: tutorial-creator-indoor-maps.md#convert-a-drawing-package
 [Creator for indoor maps]: creator-indoor-maps.md
 [Creator resource]: how-to-manage-creator.md

articles/azure-maps/how-to-create-custom-styles.md

@@ -248,8 +248,8 @@ Now when you select that unit in the map, the pop-up menu has the new layer ID,
 [map configuration]: creator-indoor-maps.md#map-configuration
 [style editor]: https://azure.github.io/Azure-Maps-Style-Editor
 [subscription key]: quick-demo-map-app.md#get-the-subscription-key-for-your-account
-[tileset get]: /rest/api/maps/2023-03-01-preview/tileset/get
-[tileset]: /rest/api/maps/2023-03-01-preview/tileset
+[tileset get]: /rest/api/maps-creator/tileset/get?view=rest-maps-creator-2023-03-01-preview
+[tileset]: /rest/api/maps-creator/tileset?view=rest-maps-creator-2023-03-01-preview
 [unitProperties]: drawing-requirements.md#unitproperties
 [Use Creator to create indoor maps]: tutorial-creator-indoor-maps.md
 [Use the Azure Maps Indoor Maps module]: how-to-use-indoor-module.md