In order to access the Master Plan you need to authenticate using the following:
All connected via Flows, IFTTT and Azure web job hooks.
In the void – bytes counts. You think that’s air you’re breathing? The Appsters wanted to improve their solution by using the public CDN functionality in SharePoint Online. It’s pretty easy to enable in a tenant. I recommend this Office Dev Center guide for how to do it, and I’m not going into details of exactly that here.
What it does is that enables a library/folder of your choice to be reached from Office 365 using a specific path on the format
https://publiccdn.sharepointonline.com/<tenant host name>/<ID of the public CDN origin>/<sub-path under the origin>
The Appsters’ public CDN URL is
We wanted to share how we work with the Public CDN and Office PnP templates. We are incorporating this into our solution using the CDN URL as a parameter into our pnp-templates.
And for the site logo:
That’s it – happy coding!
I spent some time to figure this out, so thought I would share.
We have a web job in Azure that runs a PowerShell-script that polls a list looking for new items, picks them up, creates a site collection and applies pnp templates. This works really well as a scheduled job, but it would be nicer if we could trigger the job automatically so we don’t have to wait for the scheduled start time.
It turns out that you can do this with the new Flow! Steps as follows:
That’s it! After an item is added to the list, your web job will trigger and start running. Happy coding!
Many times you might want to create services which interact with the Microsoft Graph. If your application has an actual web page you will get prompted when you visit and login to do the actual consent. If you have elevated privileges you would tack on &prompt=admin_consent to the URL and then your service can authenticate and do what you need it to.
If you just create an Office 365 entry and have no web application tied to it, this is not automatic.
One approach to get the consent URL is to create a small c# app using ADAL.
string ResourceId = "https://graph.microsoft.com"; // Microsoft Graph End-point Uri RedirectUri = new Uri("[APP ID URI]"); ClientId = "[O365 App ClientId]"; ClientSecret = "[O365 App ClientSecret]"; var authenticationContext = new AuthenticationContext("https://login.windows.net/common/"); var url = await authenticationContext.GetAuthorizationRequestUrlAsync(ResourceId, ClientId, RedirectUri, UserIdentifier.AnyUser, "prompt=admin_consent"); Console.WriteLine(url);
If you have a multi-tenant app, the above code has to be ran per tenant where the service will act against.
As the trigger action pick an HTTP Request action.
Then head over to http://jsonschema.net/#/ to generate the swagger JSON schema needed. Just enter your JSON object, any way you want, click generate schema, and copy paste the output into the Flow action.
Your object properties are now available to use in a new action, as the one picture below where we create a new CRM record.
Once you save your Flow, you can copy the endpoint URL and do a POST with your JSON object to that andpoint and you’re ready to roll
The Appsters care about great code. In fact, we care so much that we would like to see that our competitors get off on the right foot in terms of code quality, which is why we’ve submitted a pull request to the InfoAgents (the only other team with an open repo posted on the blog). We hope they like it!
All information about code/solution can be found at: https://github.com/Puzzlepart/ASPC2017
We encourage everyone to build and deploy our solution if you want to try it out!