Azure-communitysupport

Azure CLI DevOps get ID of created item with PowerShell

• azure
• powershell
• azure-devops
• azure-powershell

Mail merge word docx in Azure app service

• c#
• azure
• ms-word
• azure-web-app-service
• docx-mailmerge

Deleting external metric in Kubernetes

• azure
• kubernetes
• azure-aks
• kubernetes-external-metrics

Azure Pipelines delete files and rename after IIS publish

• asp.net
• azure
• iis
• azure-devops
• azure-pipelines

Azure VM Disk Driver Error

• azure
• virtual-machines
• drivers

What does the Interrupted status mean when reviewing Azure's Risky Login report?

• security
• azure

Azure VM cannot join domain controller

• domain-name-system
• active-directory
• azure
• domain-controller

Is it possible to sign in to Azure AAD with a Logic App or Function

• azure
• azure-active-directory

Change layout of Modern billing report (recon files) to include lower level subscription name

We have several customers migrated on Azure Plan that have multiple subscriptions. For customer internal billing we used the old Azure billing recon files to split our invoicing per subscription name. However, the Azure Plan recon files do not list the lower level subscription names anymore, but only the top level one (<customer> - Azure Plan). That breaks our ability to provide our customers with split billing. As that subscription ID column is now rendered useless (it is just customer name + Azure Plan), why not use it again for the lower level subscription names?

Support Backend IP Address Dimension for SYN Count on Azure Load Balancer Metrics

Currently, SYN Count, which is a metric describes the volume of TCP SYN packets of Azure Load Balancer, is allowed to configure with dimensions, Direction, Frontend IP Address, and Frontend Port. However, one might want to know the packet volume per backend VM, for example, to investigate the bias of load balancing. Supporting Backend IP Address dimension for SYN Count may useful for this scenario.

Enable Oauthentication 2.0 on Power Automate Service Now Connector

The Service Now Connector only support Basic Authentication. In our company the Infosec team do not allow any connection with Basic Auth. For that reason is very important enable another authentication method

Implement Password Writeback healthy support through MPN Portal

I would like to inquire about an issue in the CSP portal. For an end customer with the Self Service and Password Write Back feature enabled in Azure AD, the correct helathy status is being showed up as working,, this is only being displayed when the tenant is accessed directly through the Azure Portal (portal.azure.com), form the end user perspective. If the customer environment is accessed from the partner portal, the same features are being showed as "not working". This will undoubtedly cause issues for engineers that are trying to essentially fix an issue that is not really broken. And the CSP are going to notice their customers on a false alarm. Is there any feature for the CSP portal that can be created in order to track the healthy of these products? Or can this be fixed? Thanks.