I won’t claim that this blog post is the end all of all references for connections points to Office 365, however I wanted to start a post that shows the extensive ways that can connect to various services. First, the web interfaces for various workloads in Office 365:
Microsoft 365 Administration Portal – portal.office.com
Security and Compliance Center – protection.office.com
Exchange Admin Center – outlook.office365.com/ecp
Device Management – devicemanagement.microsoft.com
Azure ADAdmin Center – aad.portal.azure.com
Azure Portal – portal.azure.com Continue reading
Last year I published a blog post on this same topic. In this post I wanted to dive a bit deeper into what exactly is going on and possibly suggest some ‘upgrades’ to the wizard to make it easier to understand the process.
I recently ran the wizard with a client to see all the new changes and to access what we could copy and what the experience was while running the wizard. Here are my observations… and my final verdict on the experience:
(1) User Experience
This part is initially a good one. The first encounter with the change is on the ‘Hybrid Features’ screen for the Office 365 Hybrid Configuration wizard: Continue reading
For this Quick PowerShell post I wanted to share a little deep dive into Modern Public Folders (Exchange 2013 – 2019). In sharing this, I wanted to expose some of the properties of Public Folders that you may not have known were exposed with PowerShell and can only be seen in the GUI.
Finding the Primary Hierarchy Holder
One of the most important roles in Modern Public Folders is the folder with the Primary Hierarchy. This is one role that cannot be transferred either (ref article – Introduction to Public Folder Hierarchy Sync ). It is highly recommended that this Public Folder is placed on a database that is replicated to another server in a Database Availability Group (DAG).
After Microsoft switched over to Modern Public Folders, I never thought I would have to worry or dig into the underworkings as much as we did in Exchange 2010 and before. I have been proven wrong twice now. My current issue is a corruption issue where I am unable to currently move certain mailboxes, even the main Primary Hierarchy mailbox, to another database. The server is displaying all the classic signs of a storage/hard drive problem with ESE errors and write or read errors in the Application log.
What I wanted to showcase here were a couple of sample PowerShell one-liners and scripts used to move Public Folder mailboxes and Public Folders as well as monitoring the progress of these moves.
Move Public Folder Mailbox
This is an easy one to work with. If we have a Public Folder mailbox and we need to move this mailbox to another database, possible on another DAG in the Exchange environment, the move cmdlet is very similar to that of a regular mailbox move:
New-MoveRequest -Identity PFMailbox01 -TargetDatabase PF1 -SuspendWhenReadyToComplete -BadItemLimit 10
Microsoft recently made a change to their documentation on this Office 365 feature. The documentation can be found here
Ironic pic of the day:
So. The Auto-Expanding Archive part is true, it's just not the unlimited buffet of storage that it used to be. Did you see an announcement on this? I doubt it.
Tony Redmond was kind of enough to write a detailed article on the findings earlier today. Check out his blog post HERE.
The last updates for these scripts occurred in June for all three versions. In this update, .NET 4.8 is now added as the default and .NET 4.7.2 is now removed as an option.
The updated scripts can be found here:
Exchange 2019 v1.12 Prerequisite Script
Exchange 2016 v1.18 Prerequisite Script
Exchange 2013 V1.21 Prerequisite Script
Exchange 2019 v1.12 Screenshots:
** UPDATE **
Looks like Microsoft listened to all of the criticism and made some good changes. Is it perfect? No, but it is better than the original proposal by Microsoft:
** Back to the Original **
Microsoft is releasing a new ‘feature’ for the middle of November 2019 that will allow for user licensing self-service. This is not for all Office 365 licensing and is rather limited to Microsoft Power Platform (Power BI, PowerApps and Flow) subscriptions. Quick information:
You can form your own opinion here:
Self-Service Purchase FAQ
And vote for Admin blocks here:
User Voice – Admin Block of Self Service Purchase
IMHO, this is a bad idea. We have Enterprise Agreements (EAs) and IT departments to handle these functions. Companies may have legitimate reasons for blocking features in an environment for support and monetary reasons, just to name a few. To put in something like this, as an end around for IT, is a poorly thought out feature that will lead to bad things and unsupportable features enabled for end users that the IT department and management will be completely unaware of unless they are actively monitoring their licensing. There also isn’t a way to turn this off. I might have been OK with it being turned on by default IF there was a way to turn it off. Since there is not, I don’t support this feature at all.