You learn something new every day… I guess that means I’m ahead of schedule for the day.
A coworker asked if there was a way to use PowerShell to create a dynamic distribution group using one of the AD customAttributeX values. I didn’t know the answer offhand (since I create new distribution groups about every 5 years), but a little binging turned up the documentation for New-DynamicDistributionGroup. Turns out that the ConditionalCustomAttributeN parameters will do what he wanted:
It turns out that wasn’t what he really wanted– he wanted to create a dynamic DG to include objects where the custom attribute value was not set to a particular value. The ConditionalXXX switches can’t do that, so he had to use a RecipientFilter instead:
I hear you now: “Wait! You and Tony record new episodes quarterly! In California! Why are you posting a new episode already?”
Because Microsoft Ignite, that’s why! We were able to steal away to the very nicely equipped Podcast Center at Ignite to talk about some of the big announcements, rumors, and news around Office 365. (Thanks to Julian for the audio production btw.) Hear about changes to Office 365 groups, a new name for a controversial features, and what Atlanta has given the world.
Another trip to California for Tony and me means another episode of Office 365 Exposed! This time, we talked about Microsoft Ignite, Office 365 Groups, why the Saints are my favorite football team, and a host of other topics. (OK, I admit it. We did not actually talk about the Saints. Maybe next episode. I did sneak in a plug for the College Football Hall of Fame though.)
I recently had the opportunity to sit down with Tony at ENow World Headquarters (OK, it’s just a regular office, but that sounds better) to talk about the state of the Office 365 world. In this episode, we talked about the latest bit of ill behavior from Microsoft Learning, the best paths to take to gain practical Office 365 knowledge, and what to expect from the upcoming Microsoft Ignite and IT/DevConnections shows. Enjoy!
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.
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.