Newbe Dev Stack

Answer : Azure Firewall features https://docs.microsoft.com/en-us/azure/firewall/firewall-faq#what-capabilities-are-supported-in-azure-firewall Azure Firewall vs NSG https://docs.microsoft.com/en-us/azure/firewall/firewall-faq#what-is-the-difference-between-network-security-groups-nsgs-and-azure-firewall I use NSG to limit access within a vNET and Azure Firewall to limit access to a vNET from the outside. There are some good detailed explanation in the docs articles

Answer : ExecutePipline currently cannot pass anything from its insides to its output. You can only get the runID or name. For some weird reason, the output of ExecutePipeline is returned not as a JSON object but as a string. So if you try to select a property of output like this @activity('ExecutePipelineActivityName').output.something then you get this error: Property selection is not supported on values of type 'String' I found that I had to use the following to get the run ID: @json(activity('ExecutePipelineActivityName').output).pipelineRunId The execute pipeline activity is just another activity with outputs that can be captured by other activities. https://docs.microsoft.com/en-us/azure/data-factory/control-flow-execute-pipeline-activity#type-properties If you want to use the runId of the pipeline executed previosly, it would look like this: @activity('ExecutePipelineActivityName').output.pipeline.runId Hope this helped!

Answer : I finally got a working answer from Microsoft Support on this. They said that the Microsoft CDN Rules Engine does not support URL file extension Not Any and instead I should check for the length of the file extension. Condition: URL file extension Operator = Not greater than Extension = 0 Case Transform = No transform Action: URL rewrite Source Pattern = / Destination = /index.html Preserve unmatched path = No This solution works for me. Make sure to purge your cdn cache before testing. If none of your page URLs contain a dot, you can set a rule as follows: Condition: 'URL file extension' = Not Any (i.e. there is no extension) Action: 'URL rewrite', source = / destination = index.html Preserve umatched path = No This will rewrite any URL without a dot in the trailing section to index.html.

Answer : (Other answer is a bit confusing, so writing instead of editing a lot) Azure Functions can now run up to 10 minutes using the consumption plan by adding the functionTimeout setting to your host.json file: In a serverless Consumption plan, the valid range is from 1 second to 10 minutes, and the default value is 5 minutes. In the Premium plan, the valid range is from 1 second to 60 minutes, and the default value is 30 minutes. In a Dedicated (App Service) plan, there is no overall limit, and the default value is 30 minutes. A value of -1 indicates unbounded execution, but keeping a fixed upper bound is recommended Source: https://docs.microsoft.com/en-us/azure/azure-functions/functions-host-json#functiontimeout File: host.json // Value indicating the timeout duration for all functions. // Set functionTimeout to 10 minutes { "functionTimeout": "00:10:00" } Source: https://buildazure.com/2017/08/17/azure-functions-extend-execution-timeout-pa...

Answer : You should specify which version of MS Azure Storage explorer your're using. If you're using some newer versions of 1.9.0 / 1.8.1 / 1.8.0 etc.(please find more details in this link), then Azure Storage Explorer is integrated with azcopy which is using simple commands designed for optimal performance. So you can have a good-performance for downloading / uploading etc. When using code for downloading / uploading blobs, you can take use of this Microsoft Azure Storage Data Movement Library. This library is based on the core data movement framework that powers AzCopy, which also provides you high-performance uploading, downloading. I eventually tried 2 solutions proposed by @Ivan and @mjwills: DownloadToFileParallelAsync resulted in 10min 12secs Microsoft Azure Storage Data Movement Library resulted in 9min 35secs Both solutions much faster than the original DownloadToFileAsync. DownloadToFileParallelAsync is only available in later versions of the library...

Answer : Azure AD is a directory service with the goal of serving organisations and their needs for identity management in the cloud. You develop against Azure AD, you can secure your applications with it - their users in Azure AD tenants can use it. Your application is targeted for a specific organisation or multiple organisations using Azure AD (Office 365). Azure AD B2B is just a feature of Azure AD. It allows organisations to grant access to their applications and services for users from other tenants. From your app perspective nothing changes. It is still same Azure AD app. Azure AD B2B has an API which can be used to create flows for the invitation of users from another directory but it is not changing your app design, etc. Azure AD B2C is another service built on the same technology but not the same in functionality as Azure AD. Azure AD B2C target is to build a directory for consumer applications where users can register with e-mail ID or social providers like Google, ...

Answer : James, I think you already have most of it figured out. VM load balancing: Works only with VMs that are in the same region Only does Round Robin Uses a hash-based algorithm for distribution of inbound flows Works at the TCP/UDP level, routing traffic between one or more private endpoints that sit behind a public endpoint https://www.windowsazure.com/en-us/manage/windows/common-tasks/how-to-load-balance-virtual-machines/ Traffic Manager is different in that: It can work across regions It offers traffic management policies other than round robin (e.g. failover, performance) It works at the DNS level, “routing”** traffic between one or more public endpoints that sit behind a common DNS name https://azure.microsoft.com/en-us/documentation/articles/traffic-manager-manage-profiles/ You can indeed use the Load Balancer and the Traffic Manager in tandem, you hit the nail on the head there. -- Vlad ** Traffic manager does not actually route traffic, it...

Answer : for some reason, had to go with .NET Standard 2.0 instead of .NET 461, which I was previously using, along the tutorial suggestion. It seems that when you create azure function initial, your function is .NET 461 and for some reason, you change it to .NET Standard 2.0. However, when your function is .NET Standard 2.0, your runtime version should be set to beta . So add AzureFunctionsVersion in your .csproj, because the default .NET 461 runtime is 1 and when you change to .NET core, you need to change the runtime to " beta " manually. You could refer to the following code: <PropertyGroup> <TargetFramework>netstandard2.0</TargetFramework> <AzureFunctionsVersion>v2</AzureFunctionsVersion> </PropertyGroup>

Answer : There are a couple options here within App Service. I won't touch on Logic Apps or Azure Automation, which also touch this space. Azure WebJobs This article is honestly the best explanation, but I'll summarize here. On Demand WebJobs aka. Scheduled WebJobs aka. Triggered WebJobs Triggered WebJobs are WebJobs which are run once when a URL is called or when the schedule property is present in schedule.job. Scheduled WebJobs are just WebJobs which have had an Azure Scheduler Job created to call our URL on a schedule, but we also support the schedule property, as mentioned previously. Summary: + Executable/Script on demand + Scheduled executions - Have to trigger via .scm endpoint - Scaling is manual - VM is always required Continuous WebJobs (non SDK) These jobs run forever and we will wake them up when they crash. You need to enable Always On for these to work, which means running them in Basic tier and above. Summary: + Executable/Scr...

Answer : For Azure's Redis service, the Azure portal has a built-in console (which is in Preview): At this point, it's as simple as executing a flushall command: If you're running Redis in, say, a VM, you'll need to use a tool to connect remotely to the cache and run the flushall command.

Answer : Azure CLI is a PowerShell-like-tool available for all platforms. You can use the same commands no matter what platform you use: Windows, Linux or Mac. Now, there are two version Azure CLI. The Azure CLI 1.0 was written with Node.js to achieve cross-platform capabilities, and the new Azure CLI 2.0 is written in Python to offer better cross-platform capabilities. Both are Open Source and available on Github. However, for now, only certain PowerShell cmdlets support use on Linux. Is it targetted for the audience who want to manage Azure IAAS from Linux environment? I think the answer is yes. For a Linux or Mac developer, I think they more likely to use Azure CLI. Both, Azure CLI and the PowerShell package use the REST API of Azure. As one of our Microsoft contacts said: Use whatever you like and you prefer. There are some pros for Azure CLI: Open Source - which has many advantages. It might be developing faster in the future. You can view what is really in...

Answer : For trigger of one pipeline from another azure official docs suggest this below solution. i.e. use pipeline triggers resources: pipelines: - pipeline: RELEASE_PIPELINE // any arbitrary name source: PIPELINE_NAME. // name of the pipeline shown on azure UI portal trigger: branches: include: - dummy_branch // name of branch on which pipeline need to trigger But actually what happens, is that it triggers two pipelines. Take an example, let suppose we have two pipelines A and B and we want to trigger B when A finishes. So in this scenario B runs 2 times, once when you do a commit (parallel with A) and second after A finishes. To avoid this two times pipeline run problem follow the below solution trigger: none // add this trigger value to none resources: pipelines: - pipeline: RELEASE_PIPELINE // any arbitrary name source: PIPELINE_NAME. // name of the pipeline shown on azure UI portal trigger: branches: includ...

Answer : For Azure CLI 2.0 (preview) I had to use az account set --subscription <name or id> Please try the following: azure account set -s {Subscription Id} That should change the subscription. Try in this way.it worked for me to set Azure PowerShell to a specific Azure Subscription Set-AzContext -SubscriptionId "t666-e251-49ce-a1cd-5c3144"