Azure announced the ability to upgrade Azure Log Analytics workspace recently. It comes with a new query language (https://docs.loganalytics.io/index). But after the upgrade their Search REST API (https://learn.microsoft.com/en-us/azure/log-analytics/log-analytics-log-search-api) isn't working anymore. I wasn't able to find a way to execute new Search Queries via REST. I would imagine that it would be similar to AppInsights API (https://dev.applicationinsights.io/).
It also seems like they have actual API but no documentation as of yet, because Microsoft Flow has ability to integrate and execute Search Queries with the upgraded workspace (https://learn.microsoft.com/en-us/azure/log-analytics/log-analytics-flow-tutorial).
Any help in pointing on how to execute new Search API via REST is greatly appreciated.
Thanks
Documentation for new REST API wasn't available when this question was posted. Here is the MS response:
https://social.msdn.microsoft.com/Forums/azure/en-US/0c044c41-6642-4bb0-9a61-64d6f6b8b042/new-log-analytics-search-rest-api?forum=opinsights
Related
I'm having trouble with retrieving azure update management details programmatically. I couldn't find any REST API or CLI method to get the data from update management view. There were only powershell scripts.
These are the details I want to retrieve via REST API
As shown in below screenshot, currently I see only below highlighted REST API's that are related to update management. Here is the document reference for the same.
If these REST API's doesn't help to accomplish your requirement then if interested you may share it as feature request in this uservoice or feedback forum.
In general, Azure feature team would check feasibility of a feature request, prioritize against existing feature backlog, add in roadmap as appropriate and would announce and/or update the related Azure document once a feature request is addressed.
On the other hand, with the help of this references, you may find the same information in update management related kusto tables which you can query with the help of this REST API.
Here is the reference link for the same issue which was addressed in Microsoft Q&A
We have teh need to interact with our customers AD from Jira in order to handle automatically user onboarding.
For that we have 2 deifferent approach :
Using Microsoft Graph API
We call directly from Jira Script Runner plugin using groovy script POST and GEt methods, this directly within Jira environment
Using Microsoft Azure SDk for python
Using this approach will need to build a python script which is store in the dedicated location on the VM and calling that scrip from Jira using Groovy script
In the first approach we are using only 4 API call only for how request and we are all time scripting within Jira environement.
ON the second approach we need to deal with 2 types of script ( python and groovy)
Based on your advise, do you see what could be the best based on your experience in order to help me chose one or the other ?
Thanks for help
regards
See https://learn.microsoft.com/azure/active-directory/develop/active-directory-graph-api
We strongly recommend that you use Microsoft Graph instead of Azure AD
Graph API to access Azure Active Directory (Azure AD) resources. Our
development efforts are now concentrated on Microsoft Graph and no
further enhancements are planned for Azure AD Graph API. There are a
very limited number of scenarios for which Azure AD Graph API might
still be appropriate;
Hence I will suggest Microsoft Graph
I would follow up to Laurent, and say, the better solution is the solution that has the least amount of complexity while accomplishing everything you need to do.
In this case according to your own post, that is clearly just calling graph API directly from your groovy scripting in Jira.
I want to get the support requests that were added in the Azure portal under 'Help+Support' section by making an API call. I checked the REST API documentation but could not find one. Is there a REST API to get the support requests added in Azure portal?
It is not available yet, leave your feedback on this existing post here -https://feedback.azure.com/forums/266794-support-feedback/suggestions/16723438-automated-support-ticket-management for the Azure owners to review and consider this request for the future release.
This is now available, please take a look at the Documentation here:
https://learn.microsoft.com/en-us/rest/api/support/supporttickets/create
I'm trying to create a Logic Apps custom connector based on a Postman collection.
When I'm on the stage to provide the Postman collection in the custom connector blade in the Azure portal, I can't upload the collection because nothing is provided in the screen for that as shown in the screenshot :
We had a bug that recently appeared in this experience. We are rolling out the fix in a few hours. Apologies for the inconvenience. Feel free to ping me for updates if you don’t see it resolved today. Logicappsemail at Microsoft dot com
I was following the Microsoft Azure documentation to integrate my Xamarin Forms app with azure mobile services. I defined a data connection, used easy tables to define some custom tables and everything was working as expected with the mobile client.
Today I wanted to extend my backend functionality and also enable file storage. I followed the instructions found here and as soon as I created a new .NET server backend project with a StorageController and published it to azure, the entire easy table api stopped working. All calls from the mobile client fail with the following error:
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
This happens for all mobileClient.GetTable<SomeEntity>().SomeOperationAsync() calls.
My guess is that publishing the custom backend overwrote the online generated easy tables api... unfortunately I don't have enough experience with the azure cloud to figure out where I made a mistake. Is there any way of getting the auto generated easy tables api to also work with file storage?
As Mimi noted in the comments, Easy Tables is only available for the supplied Node backend, deployed from the portal. If you are using your own code and publishing that, Easy Tables and Easy API will be disabled.