I decided that I needed to post this on my blog as there are many issues out there in the Security and Compliance Center that remain to be fixed despite the obvious fact that they are broken. If you are new to the Security and Compliance Center, start with the links at the bottom in the ‘Further Reading’ section. Otherwise, keep on reading.
For the past year or so, even before I formally started ton congeal my material for my new Security and Compliance Center PowerShell book, I was running into all kinds of issues and problems. First, Get-Help was broken for sometime in I believe late 2018 and early 2019, which has since resolved itself. However, I still have little things that bother me (wrong switch on a main cmdlet, get-help missing examples, no Microsoft Docs for some cmdlets and so on.). So this blog article provides a laundry list of the items I have found and if you see this list, please comment if you have other recent issues to see if we can highlight as many as possible. For those who do comment with further issues, thank you in advance. Now, for the list and details of all the items I have discovered to date:
Issues List and Explanations
(1) Help in the Security and Compliance Center is inconsistent at the moment – some observations:
- Missing examples in Get-Help for numerous cmdlets
- Missing synopsis for multiple cmdlets
- Parameters are not always indicative of what the cmdlet accepts (misspelling on at least one parameter)
- Help in Microsoft Docs is missing for some cmdlets as well. If the Get-Help information for a cmdlet is lacking, then this will make it even worse for finding relevant examples. Some cmdlets are new, so this is understandable, but others were released very recently.
(2) Permissions to run a cmdlet are not discoverable:
When you try to get the required permissions for a cmdlet, Watson errors will occur. This error seems to be a repeatable one, no matter the tenant:
(3) DLP Keyword Dictionaries generates errors about:
Limits to uploading content (100Kb limit on file and 1MB on connection limit)
** Note ** A lot of these items have been raised for awareness or have bug reports with Microsoft already and they could be fixed by the time you read this book. No guarantees on what will be fixed, broken or otherwise because Microsoft owns and maintains the PowerShell module for the Security and Compliance Center as you would expect.
(5) Protection Alerts in PowerShell – unable to add multiple Operations:
However, notice that if we use the Set-ProtectionAlert to change the Operation value to any other value that was included in the multiple actions, They are added or changed without issue:
(6) Cmdlet issues:
Get-InformationBarrierReportDetailsGet-InformationBarrierReportSummaryNew-SupervisoryReviewPolicy2Get-SupervisoryReviewActivityNew-DLPKeywordDictionary –> File has 97000 lines:Reduce the number of lines, we eventually get this message:
This label has a parameter called Settings that is not available in the cmdlet, because it is misspelled (no ‘s’ at the end). If we look at help and check the parameters that should be available to the cmdlet, we see it is called settings:
However, if we actually try to use it we get an error:
Why? If we type in ‘New-Label -sett’ and hit tab, autocomplete for Powershell provides us with ‘New-Label -Setting’. This will work. It’s not supposed to, but it will.
As you can see by the list above, there are a lot of items that are broken or need work. If you were experiencing an issue and it was in the list above, at least you know now that you are not alone. If you have an issue you have experienced and it is not listed above, please feel free to comment. As always, if you need a book on PowerShell – Exchange, Exchange Online or the Security and Compliance Center, please visit my shop to purchase a book. Thank you for your support!
PowerShell Book Series