azure VS Azure PowerShell

Wrote a document which explains how limit access to PaaS - https://github.com/groovy-sky/azure/tree/master/paas-vnet-04 . IP is not working in some cases.

There is a problem if vendor is trying to access your storage from the Azure resource, located in the same region as the storage account (more detailed explanation here). Except that everything else seems reasonable.

Yep. Have skipped that part for a better visibility. Have wrote separate article about that - https://github.com/groovy-sky/azure/blob/master/paas-vnet-02/README.md

So was trying to make production-ready setup using Azure Private DNS resolver for accessing Private Endpoints from on-premises. Currently, self-hosted solution is used for that(wrote article about it).

We are using Private Endpoints and conditional forwarder to share access to on-prem. An example of such configuration you can read here - https://github.com/groovy-sky/azure/tree/master/paas-vnet-02 . Recently Microsoft announced which could be used for exactly same reason - https://docs.microsoft.com/en-us/azure/dns/dns-private-resolver-overview

Not for now. I already have wrote in a plain English few articles about this topic (1,2,3) with a more detailed explanation and practical examples (which you run). At least for now, there is nothing left, what I could share in that area. Probably, in the future I will try to find and tell something new about this topic :)

I have a draft of an article about this scenario - https://github.com/groovy-sky/azure/tree/master/paas-vnet-02

A time ago started to learn about resource's protection(even wrote an article about private endpoints). Now want to summarize main technologies/options in one picture. Result you can see below. What do you think? Did I miss something? I know that not every resource/SKU have possibility to use service/private endpoints, which is why used "Try" word.

Special for such use-case wrote instruction how-to use CoreDNS, which is running as container instance, to expand Azure DNS to on-prem - https://github.com/groovy-sky/azure/tree/master/docker-coredns-00

Author : Microsoft Corporation CompanyName : azure-sdk Copyright : Microsoft Corporation. All rights reserved. PublishedDate : 23-May-23 04:37:01 InstalledDate : UpdatedDate : LicenseUri : https://aka.ms/azps-license ProjectUri : https://github.com/Azure/azure-powershell #>

Get-AzOperationalInsightsDataSource

https://github.com/Azure/azure-powershell/issues/14568 looks like the Az cmdlets use the Azure Graph so likely they die as well. Would be nice if they would document that.

Since the first error is the write-warning from connect-azaccount (see GitHub) and the second is a cmdlet in that same module.

Downloads over here: https://github.com/Azure/azure-powershell/releases

You might also want to have a look at the source for some PowerShell modules, for example https://github.com/Azure/azure-powershell/

https://docs.microsoft.com/en-us/azure-stack/aks-hci/container-storage-interface-disks