Recently had to do a bunch of research into guest access in Azure AD. One of things I’ve been trying to wrap my head around recently is the move from federation access via legacy ADFS type connections. Moving those over to guest access to B2B. It really fixes some of the trust issues that would happen. It also allows the IAM part of the business to play catch up instead of trusting all domain users for example. I was at ignite this year, and it seemed to be the overall theme. Consuming content how you want to consume, via a B2B, and collaborate on the go. With all the updates to teams we’ve gotten in the last year, I am excited to see what this year has in store. 
Tag Archives: Active Directory
Assigning licenses in O365 via Okta
Recently had to set up Okta assign some O365 licenses. I wasn’t aware at that time, that this also requires me to manage all the Azure AD roles thru Okta as well. This is a pain in the ass.
New InTune User Portal
From Microsoft
User experience update for the Company Portal app for iOS We’ve released a major user experience update to the Company Portal app for iOS. The update features a complete visual redesign that includes a modernized look and feel. We’ve maintained the functionality of the app, but increased its usability and accessibility. You’ll also see: Support for iPhone X. Faster app launch and loading responses, to save users time. Additional progress bars to provide users with the most up-to-date status information. Improvements to the way users upload logs, so if something goes wrong, it’s easier to report.
For awhile now, the Company portal has been lacking behind what you get from MobileIron and airwatch, with the release this week the portal feels more modern. This has been a sorely needed update for awhile now. With a lot of firms moving off of Airwatch and MobileIron when doing Microsoft renewals. We are getting weekly updates from Intune. It surely has come a long way. 
Why you should never change the name of your mailbox server, ever.
I recently had the pleasure of dealing with a customer who renamed their Exchange mailbox servers, and the pains that went along with it. The obvious thing here is, you should never be renaming your Exchange mailbox servers, and I will attempt to explain why. The first thing to realize is that Active Directory is liberally populated with references to an Exchange server name. These are everywhere in Active Directory, so when you make this change, there is a good chance (100% certainty) that AD will not populate these changes to all the users. So why is this a big deal? Those settings in AD are the configurations that we use every single day. When you make a change to the object that active directory references, AD has no way knowing the new name of the object. This can cause you HUGE problems going forward with things like Remote-Powershell, Directory services, Calender delegates and many other LDAP objects.
Peters ramblings 