sql-docs VS azure-docs

"sql-docs/stdistance-geography-data-type.md at live · MicrosoftDocs/sql-docs · GitHub" https://github.com/MicrosoftDocs/sql-docs/blob/live/docs/t-sql/spatial-geography/stdistance-geography-data-type.md

Here are some Microsoft staff helping someone with the same issue - you could send this thread to your IT department maybe - https://github.com/MicrosoftDocs/sql-docs/issues/1886

Thanks, I've had a quick look at this, but really need to get to grips with it some more. It does seem that the XEvent Viewer does not show up for Azure databases though, only for on-premises databases (discussed here, and they don't seem to have any intention of fixing it), which put me off of my initial investigations, but perhaps now is a good time to have another look.

CREATE USER FROM EXTERNAL PROVIDER by Service Principal #2323

see also : https://github.com/MicrosoftDocs/sql-docs/issues/1594

Explained here: https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/backup/backup-azure-alternate-dpm-server.md

Official doc on runbook limitations: https://github.com/MicrosoftDocs/azure-docs/blob/main/includes/azure-automation-service-limits.md

I dont think that works:

    > git clone --depth 1 https://github.com/MicrosoftDocs/azure-docs

Does anyone have any idea why this is? I found a github issue that basically describes the issue as well but there is no satisfying solution. Can you really not use native azure monitoring solutions if you migrate your VMs to azure? That seems hard to believe and I hope I'm just missing something. I'm very thankful for any advice at this point.

It appears that there is a 512kb payload limit with runbook webhooks, which I can only find mention of on this git file:https://github.com/MicrosoftDocs/azure-docs/blob/main/includes/azure-automation-service-limits.mdThe data I was including in the web activity body appears to be just under this limit and would trigger the runbook without issue. But with the extra data webhook activities include in the body it puts it over the limit and never triggers it. Unfortunately Data Factory doesn't handle this situation properly and the activity runs indefinitely until you cancel it (despite the timeout configured).The work around for me was to add a foreach activity and put the webhook activity inside of that.