I was wondering if there is an eta on when it is possible withing Graph to create Sites / subsites directly instead of using the sharepoint rest api's?
No ETA to share unfortunately. If you're starting fresh today, I would recommend using the SharePoint PNP Provisioning engine if possible, it's highly likely that when we do introduce provisioning APIs to Microsoft Graph we'll update the PNP Provisioning engine to take advantage of them.
Related
I am looking for APIs to get list of run instances of a workflow on SharePoint Online.
From Microsoft documentation I can get list of workflows in the tenant.
https://learn.microsoft.com/en-us/power-automate/web-api
I would like to get all running workflows of a particular workflow, not only assigned to me
As far as I am aware that Web API does not have an entity for the cloud flow runs (only the desktop flow ones, which is the flowsession entity).
However, you should still be able to use the Service.flow.microsoft.com approach.
For example Stefan Strube has a nice blog on how to create a custom connector for this:
https://2die4it.com/2020/07/08/custom-connector-to-get-flow-run-history/
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 know of ARM, the REST SDK and the CLI Powershell cmdlets.
What I want to know is; which of these has the most extensive support for scripting resources without having to touch the (indeed very slow) Azure Portal?
And I would also really like to know which one of these Microsoft usually ship first with regards to preview features?
Each service in Azure is exposed using a REST API. Most of those APIs are publically supported. Some aren't.
It depends on the team that builds the elements that make up Azure and often their primary customer base. The Windows IaaS and AAD teams have been mostly PowerShell first. Machine learning and AI seem to favor azure-cli, which is built in Python, a very commonly used language in big data scenarios. The Azure Devops team has recently moved from the Visual Studio to the Azure brand (formerly Visual Studio Team Services, Visual Studio Online, Team Foundation Service preview). Their tools are mostly Node and Powershell based. Not everything in Azure is a "Resource", per se. So not all things are created or updated using Azure Resource Manager Templates (ARM).
So, unfortunately, there is no golden hammer when it comes to automating Azure.
Azure REST Api is, obviously, the best way to go, but its the least convenient (there probably is a better word for this). I really like arm templates, they (basically) allow you to define REST api calls you want to do and allow to do some looping\parametrizing\etc. As arm templates are just a proxy for the rest api, they usually work really well.
When visiting the url - https://developer.microsoft.com/en-us/graph/graph-explorer
In the graph explorer it has a drop down 1.0 or beta. Is beta version 2.0 that Microsoft references in all of it's documentation?
https://learn.microsoft.com/en-us/azure/active-directory/develop/azure-ad-endpoint-comparison
This would be a great question answered because I do not see a drop down for v2.0
There are a couple of things to differentiate here. Azure active directory is the central identity service behind most of Microsoft SaaS services.
It provides two main things
a central identity database that stores users, groups and more. It can be accessed via the graph.windows.net API. Although it's recommended to use the Microsoft graph instead now.
authentication and authorization services. That live mostly under login.microsoftonline.com.
The later provides two versions of the service v1/v2 that implement different capabilities and protocols. (Second documentation link you're providing).
The Microsoft graph on the other hand is the central API for Microsoft 365 services.
The v1 is supported for production workloads, Microsoft is not going to break the API contract and keep the services behind it up and running.
The beta endpoint is where Microsoft makes new things available to get some feedback. Not meant for production workloads. When those new capabilities are ready for prime time, they'll show up under v1.
There's no v2 as of today for the graph. They'll publish a v2 once they need to publish breaking changes to existing capabilities to avoid breaking v1 and disrupting customers.
Is it possible to create SharePoint web hooks without Azure?
I have a requirement where I need push notifications from a SharePoint list, I read that SharePoint web hooks can be used to achieve it, but customer doesn't have an Azure account and looking into possibilities where it can be achieved without using Azure.
It is absolutely possible. The premise of WebHooks is that SharePoint Online will HTTP POST to a URL you define when the event happens. The only thing that is important is that the WebHook service you create and register with SharePoint Online has to be accessible to the SharePoint Online service. Without getting into specialized networking arrangements with Microsoft this means your service has to be publicly addressable. Azure is used as a common example because it is publicly addressable, it is a Microsoft product and lots of SharePoint Online customers are also Azure customers. There is however nothing that would stop you from using your own hosting solution.
Here is a presentation on WebHooks: https://docs.com/OfficeDevPnP/1223/pnp-web-cast-sharepoint-webhooks