Exchange Hybrid Mailbox Move - Corruption Due To Missing Security Principals (ACL issues) - TooManyBadItemsPermanentException

By -
UPDATE 14 Jan 2020
---------------------
Microsoft have introduced DCS (Data Consistency Scoring) which is planned to supersede the Bad Item Limit count you declare on a migration.

 There are four grades of DCS; Perfect, Good, Investigate and Poor.  You can complete the migration for all grades, except Poor.

 Importantly, this now means they can now properly differentiate between a corruption in mailbox data and missing permissions or security principal which couldn't be set on the target mailbox. Previously you had to raise the Bad Item Limit to compensate for security principals and genuine corruption combined; this should no longer be the case.

 For now, DCS will be used by default where you don't set a Bad Item Count. If you do specify a Bad Item Count, DCS will not be used
See the below links for more details:

 https://techcommunity.microsoft.com/t5/exchange-team-blog/improving-migrations-using-data-consistency-scoring/ba-p/1105920

 https://docs.microsoft.com/en-us/exchange/mailbox-migration/track-prevent-data-loss-dcs

 ---------------------

About midway through 2016, a change was introduced to Exchange Online whereby if a security principal could not be successfully validated/mapped to an Exchange Online object, it would be marked as a bad item. Previously, the behaviour was that invalid permissions would simply be ignored, and administrators were then left to wonder why some permissions no longer worked after the migration. With this new behaviour, corrupt/invalid permissions are now logged so that administrators will know that there are problems with permissions.  The following article covers this in more detail: https://blogs.technet.microsoft.com/exchange/2017/05/30/toomanybaditemspermanentexception-error-when-migrating-to-exchange-online/?replytocom=310635#respond  
The result is that users who were granted mailbox permissions but have since left the organisation and had their AD user account deleted will show as a corrupt item when that mailbox is migrated to Exchange Online.  These errors were previously hidden from the log, but they're not marked as corruptions which means you need to raise that corruption level for your mailbox move/s.
In order to decipher which corruptions are genuine are which are related to ACL issues, you can run the following script.  The script can be run against a migration batch in PowerShell for Exchange Online to determine and output which mailbox migrations have genuine corruptions and require investigation, and which do not.
3 files will be output to directory specified with a subfolder with a timestamp prepended.
  1.     A summary CSV output including the mailboxes queried along with the details in the table above.
  2.     An output of all corrupt bad items found, including ACL security principals, should they need to be queried.
  3.     A migrations XML output for each mailbox migration - this can imported into any PowerShell session at a later date and queried; this allows you to remove the migration job but keep a logged record.


 Here is an example of what is output to screen:



https://github.com/benjaminjamesowens/ReportExchangeMailboxMigrationACLExceptions/blob/main/ReportExchangeMailboxMigrationACLExceptions.ps1






















































Comments









  1. Mitch16 August 2017 at 15:17
    This is exceptional work and super useful.  Thanks very much for the effort you've made to produce this.
    ReplyDelete
  2. Resonate12 December 2017 at 09:18
    Any way to check an individual mailbox if you have a large batch?
    ReplyDelete
  3. Meg17 June 2020 at 17:57
    Thank you so much for making my job a whole heck of a lot easier. This script rocks.
    ReplyDelete











Post a Comment



















Popular posts from this blog









Power Automate: Get first item in output







By







-














Image







One of the most annoying things about Power Automate for me is when I am trying to use the output of a previous action and as soon as I click that dynamic content button, it pops my new action into a For Each loop. It does this because the previous action could have more than 1 item returned and this would clearly fail unless it was in a loop. But if you have used the Row Count or Top option in the proceeding action, or you know full well that only 1 item will return, it is nice to avoid bloating the flow with an unnecessary loop. There are a couple of way to do this: First function You can craft your filter expression so that the output is wrapped in the First function.  This will tell Power Automate to only look at the first item. First(variables('Array')) Calling Index You can edit your filter expression to tell it which item from the source you want.  Zero being the first item e.g. variables('Array')[0] Which one to use? I use the index and the main reason is due to...








Read more










De-selectable radio buttons - Power Apps







By







-














Image







Introduction When creating a Canvas Power App you can choose from a large number of controls and specifically input controls designed to get information from the user. One of these controls is the humble radio button.  This is a good control which provides possible options without requiring a user action.  In comparison a dropdown would require the user to click to expand all of the possible options. Example radio button input One of problems with this control is the fact you cannot de-select it.  Once an option has been chosen, you can change it but you cannot undo it.  The post shows a way to make de-selecting possible in a Canvas Power App.  One simple way to achieve this is to have a button or icon next to the radio button and its OnSelect property to be Reset(rdoButton).  This is easy, but if there are many radio button controls, it could result in lots more controls on a screen or in an app.  Power Apps recommends keeping under 500 for an app and 300 maximum per page. The followi...








Read more










Assigning Windows 10/11 Enterprise Subscription Activation Licences to Hybrid Azure AD Joined Devices







By







-














Image







Introduction Starting with Windows 10, version 1703, Windows 10 Pro supports the Subscription Activation feature, enabling users to “step-up” from Windows 10 Pro to Windows 10 Enterprise automatically if they are subscribed to Windows 10 Enterprise E3 or E5. The Subscription Activation feature eliminates the need to manually deploy Windows 10 Enterprise or Education images on each target device, then later standing up on-prem key management services such as KMS or MAK based activation, entering GVLKs, and subsequently rebooting client devices. It’s important to note that the Windows 10 Enterprise subscription activation is designed to “step-up” a device from Windows 10 Pro to Windows 10 Enterprise. Therefore, your device is required to have a Windows 10 Pro license activated as a baseline. For Windows 10 Enterprise Subscription Activation to function, there a several prerequisites which need to be in place. This blog is aimed for organisations which have Active Directory on premises an...








Read more