Yay! Microsoft has updated their downloadable Visio stencil set for Office 365 to include the 2016 versions of the application icons, plus some other visual improvements. Now your Visio diagrams can have that fresh 2016 feel. (Thanks to Samantha Robertson, Dan Fraser, and Tony Smith of Microsoft for making this happen.)
Category Archives: UC&C
This is a great example of Microsoft bringing useful innovation to end users by deploying new features in Office 365:
Outlook on the web now makes it easier to clear your calendar and automatically decline meetings before you head out for some time away from the office. When you set an automatic reply in Outlook on the web, Outlook will offer to do the following on your behalf:
- Block your calendar so people know you’re away.
- Clear existing meetings on your calendar by declining/canceling them.
- Automatically send a response to incoming invitations while you’re away.
Of course, Outlook and Exchange have long had the ability to automatically send an out-of-office (or “OOF”, from “out of facility“) message when you specify the dates when you’ll be away. These new features extend the traditional OOF behavior by adding some business logic to the OOF process– after all, when you’re out of the office, it is logical to assume that you won’t be accepting appointments during that time, and that you want new invitations to be automatically declined. (There are exceptions, of course, which is why you can turn this business logic off.) I’m not in love with the fact that this feature requires you to set your works in Outlook on the web, but I’m hopeful that it will make it into other versions of Outlook at some point.
Apart from the specifics of this individual feature, it’s really encouraging to see the Outlook team invest in innovation like this. Given the large feature gap between Outlook on the web and Gmail (the only real enterprise competitor to Exchange/Outlook) it would be easy for the Outlook team to coast. Part of the ethos of building software at cloud speed involves iterating rapidly, and that in turn means sometimes you build something that turns out to get a lukewarm reception because it’s not as useful as first thought. (Tony argues that this is the case for Outlook’s support for likes and @ mentions.) However, sometimes you build something that turns out to be really nifty, and I think this feature is a good example– I look forward to seeing it roll out more broadly.
(for another time: I know not every tenant admin will want this feature turned on for their users without prior notice or permission, and Microsoft has a lot of room to improve the way they deliver features so that administrators can control user access to them.)
It’s the offseason for Office 365, at least sort of– with no conferences until the fall, Tony and I had to take the opportunity of meetings at ENow to record this episode of Office 365 Exposed. Topics we covered included Delve Analytics, the contentious topic of mailbox anchoring, a bit about Skype for Business Online’s telephony features, and frequent mentions of Yammer for those of you who like to enjoy our podcast with a beverage in hand.
It is a cliché to talk about an opportunity that’s too good to refuse (not to be confused with an offer you can’t refuse), but sometimes it doeshappen.
I am very excited to announce that, effective 26 October 2015, I will be taking the position of chief technology officer (CTO) for ENow Software. In that role, I will be driving the development of their next generation of products for both on-premises and Office 365 monitoring. It’s a big step forward for my career, moving me simultaneously back towards the development world and further into the cloud. (It’s also a little surreal to see one’s job change announced in a press release.)
Before I get into the nuts and bolts of what I’ll be doing, a personal note: I want to thank Scott Edwards, Ben Curry, and all my coworkers at Summit 7 Systems. What a talented and skilled group of people! I accidentally learned much more than I expected about SharePoint from them, and both Ben and managing consultant Matt Whitehorn were instrumental in helping me identify soft skills I need to work on— always a challenge. I have huge respect for what the Summit 7 team has accomplished and recommend them in the highest possible terms to anyone who needs Office 365, Azure, AWS, or SharePoint design, strategy, or migration help.
So, the new job. In the CTO role, I’ll be reporting directly to Jay Gundotra, the CEO. I’ll be responsible for technical product strategy and implementation, the customer success team, technical presales, and internal IT. (I am still working on a transition plan to establish an ENow corporate aviation department, but don’t tell Jay.) That’s quite a broad scope, which means I can bring to bear everything I’ve learned throughout my career as a developer, consultant, and administrator. Driving beneficial change across these disparate fields is going to be an exhilarating challenge! Luckily I will have a really powerful team on my side, including Michael Van Horenbeeck (noted hooligan/tequila drinker, Microsoft Certified Master, and Exchange MVP) and Tony Redmond, a member of ENow’s advisory board.
ENow is already very successful in their chosen markets, but the cloud poses a brand-new set of technical and business challenges, both for them and their customers. The #1 question I hear from IT pros and business decision makers is simple: how will the move to the cloud affect me and my business? It’s interesting that I don’t remember many people asking that during the years-long transition from mainframe- and mini-based solutions to the x86 world; people just naturally assumed their skills would transfer. That hasn’t been the case with the cloud. Figuring out how to effectively monitor and manage cloud services when you don’t control the underlying platform is a tough problem. Instrument flight is probably a good metaphor here. On a clear day, you can see the ground, so flying is easy. There’s a visible horizon and landmarks. In the clouds, everything changes– if you’ve ever been in an airplane on a cloudy day, you know that you can see where the clouds are but not what’s inside them. Flying inside clouds is like being inside a ping-pong ball, with no visual cues you can use for orientation. You have to use your instruments to keep the plane pointed in the right direction and right side up. Moving workloads such as Exchange email or SharePoint to the cloud doesn’t lessen your need to monitor what’s happening, it just changes the way in which you’ll do it, and figuring out that change is a key task in my new role.
Of course, Microsoft is releasing new services and capabilities in Office 365 at a rapid clip, so another key challenge will be figuring out how to keep up with them and how best to bring ENow’s experience in simplifying the complexities of enterprise application monitoring to a world where Microsoft seems intent on giving everyone Fisher-Price-style monitoring and reporting tools.
Despite the new job, some things won’t change: I’m still living in Huntsville, I’m still not a Cowboys fan (sorry, Jay), and I’ll still be blogging here, although I expect to be writing some more strategy-oriented posts for ENow’s blog. Where I can, I plan to share details of what I’m working on, so stay tuned!
Last year, Tony and I started producing a podcast for Windows IT Pro called “Exchange Exposed.” It was moderately successful, but the demands of producing and delivering the podcast on a regular schedule didn’t mesh well with Penton’s plan for world domination, so Tony and I took back the rights to the podcast and are recording and distributing it ourselves. However, because of some peculiarities of the way the iTunes Store lists podcasts, we couldn’t just add new episodes to the existing podcast… but we didn’t find this out until the current episode was recorded and ready.
Going forward, we’re retitling the podcast to “Office 365 Exposed” to reflect the reality that Exchange and Exchange Online are part of the Office 365 family. Unlike some other Office 365-branded media that focuses exclusively on SharePoint, we’ll be covering the non-SharePoint part of the ecosystem with vigor and depth. There’s a lot to talk about!
In this episode, recorded at IT/Dev Connections in Las Vegas, we get some quality time with special guest Bhargav Shukla of KEMP Technologies to discuss the release of Exchange 2013 CU10, the impending release of Exchange 2016, and what the future of on-premises Exchange looks like. Give it a listen below. In a day or two, iTunes should pick up the feed and you’ll be able to subscribe, or you can point your RSS feed reader to the “Podcasts” category here.
Microsoft has a really complex infrastructure for deploying new features into Office 365. This deployment process, internally known as “flighting,” involves rolling out code changes across a huge base of servers— by some estimates, more than 600,000 worldwide— spread across dozens of data centers all around the world. This poses an interesting challenge. Flighting has to be automated because of the scale necessary, but with an automated tool that works at high scale, you can make a quickly replicated mistake. Think of it like shooting yourself in the foot with a machine gun.
Recently one of my customers notified me that they had noticed a change in their tenant: each user with an E3 or E4 license was now showing a possible total of 10 product activations for Office 365 Pro Plus. The limit had previously always been 5, meaning each user may install Pro Plus on up to five PCs and Macs. The release of Office applications for Windows 10, iOS, and Android devices changed things slightly; you were allowed to install on 5 PCs/Macs plus 5 tablets or mobile devices. At various times I’ve been told that the limit was 10 (5 PC + 5 devices) and 15 (5 PC + 5 tablet + 5 phone), but in any event, the user interface in the Office 365 management tools has always reported per-user activation as N installed copies out of a maximum of 5.
Immediately upon hearing this, I checked my tenants. Sure enough, now my tenant users were showing a maximum of 10 installs.
I followed up with some local Microsoft folks and was told that they were told by Office 365 support that this was a mistake, whether in flighting or configuration I’m not sure. However, two-plus days later, tenants are still showing 10 activations. I took the below screenshot a few minutes before writing this post; it shows 4 activated Pro Plus installations, with 6 more available.
I’m going to reach out directly to the O365 team to ask whether this is: a) a temporary mistake that will be reversed b) a policy change that hasn’t been officially announced or c) a restatement of the 5 PC/Mac + 5 device policy that was already in place. I’ll report back what I find out.
Over at my work blog, I have a post that tackles an important issue: how do you reliably design and operate Exchange if you don’t happen to have a large team of Exchange rock stars on staff? (Short answer: hire me. Longer answer: read the post to find out). Bonus: the post contains a picture of
Ross Smith IV Yoda.