Feedback by UserVoice

Jeremy Bradshaw

My feedback

  1. 11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jeremy Bradshaw commented  · 

    Darn, I'm out of votes. In Exchange 2010/2016 coexistence, I don't see this error you mention, but I do know of this KB article:
    https://support.microsoft.com/en-ca/help/2956029/migrationpermanentexception-cannot-find-a-recipient-that-has-mailbox-g

    The only thing is, MS won't be rushing to fix that, since that issue only prevents offboarding from EXO, ha ha ha..

    ExchangeGuid, a.k.a. msExchMailboxGuid, should totally 100% be included in the Hybrid Exchange writeback properties list.

  2. 23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jeremy Bradshaw commented  · 

    I'm all out of votes, but I would vote otherwise.

  3. 30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
  4. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Office 365 Security & Compliance » Auditing  ·  Flag idea as inappropriate…  ·  Admin →
    Jeremy Bradshaw shared this idea  · 
  5. 191 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jeremy Bradshaw commented  · 

    Still only 174 votes. I don't understand. At least please tell us why this is possible for Room/Equipment mailboxes but not Shared mailboxes. What is the difference that merits Shared mailboxes being left out from this capability.

    Jeremy Bradshaw supported this idea  · 
    An error occurred while saving the comment
    Jeremy Bradshaw commented  · 

    +1 for this. It is vital. I would at least like to see the clear explanation for why it is not possible already. There must be some reason. What is it?

  6. 19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Jeremy Bradshaw supported this idea  · 
    An error occurred while saving the comment
    Jeremy Bradshaw commented  · 

    This is a copy paste from my comment on a similar idea, but it applies here too:

    FYI: Use Connect-ExoPSSession with the UserPrincipalName parameter and specify your UserPrincipalName along with it. This allows for seamless refresh token refreshing the (can't remember the name) other token - in other words seamless automatic re-logins.

    Checkout my Connect-Exchange function (a.k.a. conex) which makes use of the EXO PS module from a regular PowerShell window. It also should have -UserPrincipalName provided for seamless / automatic re-logins. https://github.com/JeremyTBradshaw/PowerShell/blob/master/.functions/Connect-Exchange.ps1

    For error handling to make your scripts able to deal with regular session drops to EXO, throttling, and more, checkout my script Get-ADAutoMappingFullAccessStatus.ps1: https://github.com/JeremyTBradshaw/PowerShell/blob/master/Get-ADAutoMappingFullAccessStatus.ps1. I still need to take the multi-catch by error type technique and turn it into a modular/reusable function, but the logic is shown there in the script. That script will run without error against any sized Exchange Online environment and not be phased by connection interruptions or throttling.

    I am soon going to summarize the Exchange Online PowerShell error handling techniques I've/I'm learned/learning on my Wordpress site www.jb365.ca.

  7. 269 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jeremy Bradshaw commented  · 

    FYI: Use Connect-ExoPSSession with the UserPrincipalName parameter and specify your UserPrincipalName along with it. This allows for seamless refresh token refreshing the (can't remember the name) other token - in other words seamless automatic re-logins.

    Checkout my Connect-Exchange function (a.k.a. conex) which makes use of the EXO PS module from a regular PowerShell window. It also should have -UserPrincipalName provided for seamless / automatic re-logins. https://github.com/JeremyTBradshaw/PowerShell/blob/master/.functions/Connect-Exchange.ps1

    For error handling to make your scripts able to deal with regular session drops to EXO, throttling, and more, checkout my script Get-ADAutoMappingFullAccessStatus.ps1: https://github.com/JeremyTBradshaw/PowerShell/blob/master/Get-ADAutoMappingFullAccessStatus.ps1. I still need to take the multi-catch by error type technique and turn it into a modular/reusable function, but the logic is shown there in the script. That script will run without error against any sized Exchange Online environment and not be phased by connection interruptions or throttling.

    I am soon going to summarize the Exchange Online PowerShell error handling techniques I've/I'm learned/learning on my Wordpress site www.jb365.ca.

    Jeremy Bradshaw supported this idea  · 
  8. 312 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    19 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Jeremy Bradshaw supported this idea  · 
  9. 33 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Office 365 Security & Compliance  ·  Flag idea as inappropriate…  ·  Admin →
    Jeremy Bradshaw supported this idea  · 
  10. 1,213 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    133 comments  ·  Office 365 Admin » Message Center  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jeremy Bradshaw commented  · 

    This issue is most invasive when doing a large migration from Exchange on-premises to Exchange Online when you have lots of migration batches. It's such a bad "feature".

    It's really annoying.

    Jeremy Bradshaw supported this idea  · 
  11. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General » Uncertain topic  ·  Flag idea as inappropriate…  ·  Admin →
    Jeremy Bradshaw shared this idea  · 
  12. 400 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thanks for taking the time to provide this feedback. We’ve updated the TechNet documentation (https://technet.microsoft.com/library/mt842508(v=exchg.150).aspx) to clear up confusion around which authentication type and protocol combinations are supported in CARs. Expanding support for more combinations could prevent bad actors with valid credentials from accessing mailbox content, but it wouldn’t help with scenarios like password spray attacks or malicious lockout attempts because CARs are evaluated post-authentication. There’s work underway on a solution that covers a broader array of basic authentication scenarios – we’ll share more details as soon as possible. In the interim, this blogpost (https://cloudblogs.microsoft.com/enterprisemobility/2018/03/05/azure-ad-and-adfs-best-practices-defending-against-password-spray-attacks/) outlines the recommended approach for forcing multi-factor authentication when using AAD and ADFS.

    Jeremy Bradshaw supported this idea  · 
  13. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Jeremy Bradshaw supported this idea  · 

Feedback and Knowledge Base