Feedback by UserVoice

Kevin C

My feedback

  1. 60 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 » eDiscovery  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Kevin C commented  · 

    Right now, you can create your search, make the Export Action and have it start, but you still have to open the GUI to actually DO the export through the GUI by going to https://protection.office.com/?ContentOnly=1#/contentsearchbeta and then using the download button to start the eDiscovery Export Tool

    https://i.imgur.com/SjJTV3w.png

    In the old search New-MailboxSearch we had the option to copy search results to a discovery mailbox through powershell (Set-MailboxSearch with the -TargetMailbox param), so we could "export" to the discovery mailbox, but now this is the simplest export option, and it requires GUI

    Kevin C supported this idea  · 
  2. 2,086 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Kevin C supported this idea  · 
  3. 799 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    34 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Kevin C supported this idea  · 
  4. 46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Kevin C supported this idea  · 
    An error occurred while saving the comment
    Kevin C commented  · 

    Not to mention that connecting to these is often MUCH harder.
    If I want to connect to the Exchange Online shell, it runs from a .application

    If I want to load that in another session (Say, VS Code to work on some scripts with it) the best I have found is below.

    function Start-ExoPSSessionCmdlets {
    Import-Module $((Get-ChildItem -Path $($env:LOCALAPPDATA+"\Apps\2.0\") -Filter Microsoft.Exchange.Management.ExoPowershellModule.dll -Recurse ).FullName|?{$_ -notmatch "_none_"}| sort LastWriteTime -Descending | select -First 1)

    $EXOSession = New-ExoPSSession -UserPrincipalName user.name@domain.com
    Import-PSSession $EXOSession
    }

    But when $EXOSession dies, I have to Get-Module to find the one with a random name like tmp_iq12uju5.tgs and removing it or maybe.....
    OK. so I can automate finding it by finding the one providing get-mailbox
    (Get-Module ) | where {'Get-mailbox' -in $_.ExportedCommands.Keys} | Remove-Module

    And remove the PSSession before connecting again. Pain **********.

    Can we not just make this into something we can install like MSOL or AzureAD?

    If you need multiple modules, it's a huge pain to pull in 2FA modules from so many places

Feedback and Knowledge Base