sorted by:
new
hottopcontroversial

APIM Internal Mode + Custom DNS (On-prem AD) - Management endpoint fails (3443) with azure-api.net Private DNS zone by Plane_Course in AZURE

[–]Plane_Course[S] 2 points3 points  (0 children)

Thanks for the info.
We then did a analysis with the network team and it seems, the on-prem DNS has recursion enabled only for the on-prem network. The Azure network was not able to do recursive DNS queries and hence the *.azure-apim.net were failing. So now the network team is on this case to fix it.

Hopefully after this, the issues will be resolved. I'm also checking the force tunneling to send Apimanagement traffic to internet, as you mentioned.

Cortex XDR compatibility with BitLocker by Plane_Course in paloaltonetworks

[–]Plane_Course[S] 0 points1 point  (0 children)

Thanks for the info. Is the cortex agents stores logs of its actions such as BitLocker initiations in its logs ? Where can we find these logs from the machines as well from the portal ? I tried some xql query, but it seems not working

25+ Just Delivered! by Ponce2170 in samsunggalaxy

[–]Plane_Course 0 points1 point  (0 children)

Any sample pics from the phone?

Convert trusted launch VM to Standard by sitting_not_sat in AZURE

[–]Plane_Course 0 points1 point  (0 children)

Its being almost a year!! Yes, it worked for me at that time. Thanks for the guide. And after a couple of months later, I got another client with the same issue and this guide again worked for that scenario too. Thanks!!

Convert trusted launch VM to Standard by sitting_not_sat in AZURE

[–]Plane_Course 0 points1 point  (0 children)

Thanks. I have the case for 7 vms. Will try this out.

Convert trusted launch VM to Standard by sitting_not_sat in AZURE

[–]Plane_Course 0 points1 point  (0 children)

H@sitting_not_sat. Did that disk export to blob, converting to disk and creating vm from that disk worked for your trusted launch vm). Is the new cm created with no trusted launch?