ngrok is a fantastic tool, that I use on an everyday basis when building solutions cloud. It allows me to host and debug an application locally and at the same time host the website or API’s with a publicly accessible https endpoint. As I work quite a bit with Microsoft Teams development this is essential when building bots (Azure Bot Service cannot talk to localhost) or building out Teams Tabs with SSO.
When you’re working with building applications or services there’s always a need to store configuration. For Azure there’s a great service called Azure App Configuration that allows you to securely store, manage and retrieve configuration settings. It’s a perfect service for both smaller and larger projects and it keeps your configuration in control, and of course secured and audited. When I’m building solutions using node I typically start with storing my configuration in a local .
I’ve been building chat-bots for a while now and I’m seeing more and more requests of building these bots for enterprises. For bots targeted at the enterprise, perhaps being hosted in Microsoft Teams, one of the first requirements is that they should get data from their internal systems and most specifically from Office 365, through the Microsoft Graph. The problem here is that we need to authenticate and authorize the user, through Microsoft Azure AD, to be able to access these resources.
The time has come for me to do, as I’ve done now for eight years (2013, 2012, 2011, 2010, 2009, 2008, 2007 and 2006), my annual post to sum up the year. It is always fun to look back to what happened the past 12 months. This past year has been a somewhat “in-betweeners” year. We (me, my clients, colleagues etc.) are standing on the edge of something big and the bridge over to the other side is really, really long.
I’m so excited to be once again going to Singapore and speak at the Share-The-Point Southeast Asia 2014, held November 25-26 2014. It is one of my favorite conferences and this will be my third time in the awesome country and city of Singapore! Everything is just great about this; the people, the speakers, the attendees, the city, the food – you name it! This year I will have two sessions:
After doing the Microsoft Cloud Show interview with Andrew Connell I thought it might be a good idea to write some of my tips and tricks for running SharePoint 2013 on Azure IAAS. Some of the stuff in this post are discussed in more depth in the interview and some things we just didn’t have time to talk about (or I forgot). I really recommend you to listen to the podcast as well and not just read this post.
A couple of weeks back I was interviewed by Andrew Connell for the Microsoft Cloud Show. The Microsoft Cloud Show is an (almost) weekly podcast where Andrew (AC) and his wingman Chris Johnson (CJ) discusses everything related to Microsoft cloud offerings including benchmarks with other cloud vendors. If you’re not subscribing and listening to the show already then I urge you to do that as soon as possible! Me and AC sat down for almost an hour discussing Microsoft Azure IAAS and specifically when running SharePoint 2013 in that service.
For no one out there, in the SharePoint space or any other space, Microsoft Azure has gone unnoticed. Microsoft Azure is a really great service, or rather set of services, that for a (Microsoft or SharePoint) developer or IT-Pro is something that they should use and embrace. Personally I’ve been using Azure since the dawn of the service and I’ve been using it more and more. I use it to host web sites, host SharePoint and Office Apps, Virtual Machines, Access Control and a lots of other things.