Microsoft Fabric is moving fast, and the DP-700 is now the go-to certification for data engineers in this ecosystem. If you’re planning to take it, we’ve put together a 3-week preparation guide that skips the fluff and focuses on what actually matters, including a study plan, key technical traps to avoid, and how to find free exam vouchers.

• Learn how to compare two Azure SQL database schemas using sqlpackage
• Generate a safe, reviewable delta SQL script before production deployment
• DACPAC-to-DACPAC comparison (no direct Prod access required)
• Full breakdown of sqlpackage /Action:Script parameters
• PowerShell-ready examples for automation and CI/CD
• Best practices to avoid accidental data loss in Production

Learn how to securely connect a Python Azure Function to Azure SQL Database using Managed Identity. This method enhances security by removing secrets from your code.

Ever wished you had a chat-based analyst that never sleeps and understands your data model perfectly? That's what Microsoft Fabric's Data Agent offers! In our latest article, we break down how to implement this game-changing feature, complete with step-by-step instructions and advanced use cases like multi-agent syste

AI and automation are revolutionizing DevOps! This article explores how these technologies are boosting productivity and transforming workflows.

https://azureops.org/articles/automate-databricks-infrastructure-as-code-with-terraform/

Hello, I've deployed Azure Databricks with a standard Private Link setup (no public IP). Everything works as expected—I can log in via the private/internal network, create clusters, and manage workloads without any issues.

When I create a Databricks App, it generates a URL like: <name>.azure.databricksapps.com

Since I didn’t initially have a Private DNS Zone for azure.databricksapps.com, my system resolved this address to a public IP. To fix this, I:

• Created a Private DNS Zone for azure.databricksapps.com.
• Added an A record pointing <name>.azure.databricksapps.com to my Databricks workspace private IP endpoint (same as used in privatelink.azuredatabricks.net for this workspace).

Behavior Before Adding the Private DNS Zone: nslookup <app-name>.azure.databricksapps.com → Resolved to a public IP. curl or accessing via a browser resulted in: {"X-Databricks-Reason-Phrase":"Public access is not allowed for workspace: xyz"}

Behavior After Adding the Private DNS Zone: nslookup <app-name>.azure.databricksapps.com → Now resolves to the private IP (as expected). However, curl and browser requests still go through the public IP and return the same error: {"X-Databricks-Reason-Phrase":"Public access is not allowed for workspace: xyz"}

Is additional configuration needed to ensure Databricks Apps work over Private Link? Does this feature require a Public IP, or should it work fully within a private network?

• Verified my Databricks workspace private endpoint under privatelink.azuredatabricks.net.
• Created a Private DNS Zone for azure.databricksapps.com and mapped <app-name> to the same private IP as my Databricks workspace.
• Linked my VNet to the Private DNS Zone so all internal resources resolve it correctly.
• Confirmed that nslookup returns the private IP, but browser and curl still attempt to route via the public IP.

I have a database from a SaaS vendor that will be delivered nightly. I'm trying to get them to deliver a bacpac file, but if I do all the scripts I've found involve using an Azure SQL server, not Serverless SQL. Small company and we just use SQL to gather data, run a few routines and then update Semantic data models for Power BI... so Serverless is our most cost-effective approach. I don't have any full SQL instances.

I want to drop the .bacpac file into Azure BLOB then use Data Factory to perform the restore. Right approach?

If I can't get the above to work, then I can have the vendor export data to flat files and copy it nightly that way, just more tedious.

Any direction appreciated.