As the dust settles on Microsoft Ignite for another year I’m left going back over my notes and recalling discussions I had for all those key announcements, advice and snippets of gold that will have a real impact for Office developers.
If you are looking for a high level list of announcements made at the conference, the Ignite Book of News is a good place to start although it doesn’t cover many of the announcements that were made in the Office Developer area – this book covers a lot of the Azure announcements, which most Office developers will have a mild interest in (we have to host our code somewhere!)
Here’s some of my favourite announcements:
Do more with new upcoming SharePoint development capabilities announced at Ignite 2018
- Call Microsoft Graph and Web APIs and deploy Extensions across your SharePoint sites
- Deploy your web parts and application pages to Microsoft Teams
- Connect across components with dynamic data capabilities
- Deliver complete applications with application pages
- Harness more of SharePoint with new Microsoft Graph APIs
- Managed access to Microsoft Graph (data connect to bulk export to Azure subscription)
- Notifications API
- Dynamics is now in Microsoft Graph
- New PowerApps templates
- Security API
- Microsoft Teams, Messages, Calendars, Files, and Folders
Microsoft Authentication Library (MSAL)
- In preview but suitable for production use
- Capable of reaching both v1 and v2 services
- MSAL JavaScript library for serverless implicit flow scenarios
I thought this years conference was very well run and the volume of people moving about the conference centre wasn’t overwhelming. I had a lot of fun meeting new people and reconnecting with old friends. It’s great to have such knowledgeable Microsoft staff accessible on the expo hall floor (both from a Marketing and Engineering side) to discuss particular scenarios, technologies, ad bounce ideas off.
“Do more with new upcoming SharePoint development capabilities announced at Ignite 2018” is a dead link
LikeLiked by 1 person
Thanks for letting me know. Link is now fixed 🙂
LikeLike