Forum Widgets
Latest Discussions
Data Sink From Dataverse to Azure SQL database using azure data factory is taking really long time
Hi Everyone, Actually I'm new to the azure data factory, we are facing 2 problem while sinking data verse to azure SQL database for reporting purpose. Problem 1: We have created a azure synapse link to push the data to the azure data lake from there we are pushing data to Azure SQL DB using Azure Data Factory pipelines and data flows, Using source data as Data lake data from Dataverse and Sink as dataset from the Azure SQL Database but this process is taking time. More than 9mins to sink 32 tables. Each table contains less than 2000 rows on average. and One table contains 250k rows is there a way to reduce the time of this process? Problem 2: We are have an issue with triggering the pipelines. Is there any way to trigger on data change? If any data is changed in the data verse then the pipe line should trigger and update the respective record or table in the Azure SQL DB. Please help me in this.Azure Local - Design the infrastructure - some bad design choices I have stumbled on
Hi. I wanted to share my lasted blog article where I touch on some of the bad design choices I have stumbled on when working with customers existing Azure Local deployments that broke down or in other ways behaved with poor performance or disruptions. https://www.chkja.dk/2025/07/16/azure-local-design-the-infrastructure/ I hope to inspire and feel free to share your knowledge here in the thread :)
Alert on Pending Updates
Hi, We've set up several onpremise servers with the Azure Arc agent, to allow us to manage updates via Azure Update Manager. I'd like to get a mail notification with pending updates before the maintenance is scheduled. Azure Update Manager provides a New alert rule (preview) feature that allows me to setup a new alert for pending updates easily. The issue is that it runs every 5 minutes, fires the alert, and sends the email every 5 minutes. Ideally this is sent before the maintenance schedule runs (every 2 weeks), so I know which updates will be applied before they get applied. Changing the frequency of evaluation can be changed to 1 day max, but that will trigger the message to be sent every day. I figured that I could edit the alert rule and change the Query type to Single event (preview), but not sure if that's the solution. When I try this, I cannot edit or save a query. No way to add something to the query and there's no save button: Any idea how I could trigger a Pending Update alert rule to run on a scheduled basis, eg every 2 weeks ? Thanks Best regards, Joeri Michiels
LAB: Onboarding On-premises Machine to Azure Arc by using Proxy as Connectivity Method
What is Azure Arc? Azure Arc is a set of technologies that extends Azure management and enables Azure services to run across on-premises, multi-cloud, and edge environments. It allows you to manage resources such as servers, Kubernetes clusters, databases, and applications running outside Azure using familiar Azure tools and services like Azure Policy, Azure Monitor, and Defender for cloud. With Azure Arc, you can bring these resources into Azure's control plane, standardize operations, and apply consistent security and governance across your entire IT landscape. This simplifies hybrid and multi-cloud management while leveraging Azure's features, making it easier to innovate and maintain control over your infrastructure. LAB Architecture Lab pre-requisites: Set up and on-premises environment with an VM and Enterprise Proxy. An Azure subscription where we can on board machine. Understand the system, network pre-requisite. Plan Deployment Please note the hostname as this will show in azure arc portal once you on board machine into azure arc. Also, you can verify whether proxy is configured using command netsh winhttp show proxy Note: You don't need to use proxy connectivity option if your internet traffic is already routing via proxy in the network level. You can use this option if you need your agent to communicate via a different proxy which not already configured at network level. Steps to deploy: Generate Script to on-board on-premises machine: Go to Azure Arc-->Machines and Click on Create. Select an option best suited for you. I am using Add multiple servers Option Fill the details, provide your proxy sever URL. Provide service principal already have or create new one. Provide tags if you need. Go to download and run script option. Either you can download or copy the script and directly and run it in your machine. Update Service Principal secret inside script then the script is ready to use. Run the script in on-premises machine Go to on-premises machine PowerShell and run script. The script will install the Azure Arc agent and connect the system with Arc control Plane. Not necessarily these steps need to do by PowerShell. You are having multiple way to connect machine to azure arc. Eg: CLI, API calls etc. Please go through Azure arc documentation to know more. The following action will take place once you run the script. Azure Connected Machine Agent Installation Setting proxy configuration Connect machine to Azure Now your machine is onboarded, and you can enjoy all the services in azure. In nutshell you can treat your on-premises machine as azure vm and apply all the related series.Creation of an AKS Hybrid Cluster is not working from Azure Portal
The creation of an AKS hybrid networks for Azure is failing with the error below. The resource operation completed with terminal provisioning state 'Failed'.\",\"details\":[{\"message\":\"Warning: rpc error: code = Unknown desc = rpc error: code = Unknown desc = VMMS only supports using an existing 'Default Switch' ICS network (invalid network name: 😞 Invalid Input Any assistance please?
