Feedback by UserVoice

Andrew Schwalbe

My feedback

  1. 260 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Andrew Schwalbe supported this idea  · 
  2. 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  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew Schwalbe supported this idea  · 
    An error occurred while saving the comment
    Andrew Schwalbe commented  · 

    This is still a problem a year later. We need more timely information. I'd even settle for an hour or two behind but an entire day is unacceptable in some scenarios. If the report cannot supply this information, this information should be available through a message trace and it cannot be obtained there either.

  3. 48 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Office 365 Security & Compliance » Reports  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew Schwalbe supported this idea  · 
  4. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Andrew Schwalbe commented  · 

    Agree waiting an entire day to view the encryption report is too long. If a user sends an email out I should be able to run a report or check a log to see if they enabled message encryption.

    This is important when using DLP to warn administrators that potential confidential information left the organization. Leadership should not have to wait an entire day before I can find out if a specific message used OME encryption (not applied via transport rule, applied by the user).

  5. 372 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Office 365 Admin » Service Health Dashboard  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew Schwalbe supported this idea  · 
    An error occurred while saving the comment
    Andrew Schwalbe commented  · 

    I want to make this information easily available in SharePoint for my associates so they don't have to ask our IT team every time something is goofy. It drags on our limited resources and would provide great value for all users to be able to see what is down, if anything, and incident information.

  6. 10 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  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Andrew Schwalbe commented  · 

    I haven't been able to track this down yet either. Did you ever find an answer? Is it the same thing as Office 365 Advanced Message Encryption? https://docs.microsoft.com/en-us/office365/securitycompliance/ome-advanced-message-encryption

    Andrew Schwalbe supported this idea  · 
  7. 876 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    67 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →

    Following up on the previous update, if a workload (such as Planner) is enabled for Outlook by default, we don’t plan on hiding those groups from the GAL. The only other scenario currently under consideration where we would hide groups by default is “Secret Groups”. “Secret Groups” would be hidden from everywhere unless you are a member. “Secret groups” is on the Microsoft 365 Groups backlog, but there is no delivery date available at this time.

    Andrew Schwalbe supported this idea  · 
    An error occurred while saving the comment
    Andrew Schwalbe commented  · 

    This is definitely a needed feature. Bonus if we can make secret the default option for newly created groups. We like having the flexibility for associates to create their own groups, but it is destroying our GAL and the option of hiding all the groups from the GAL, although workable, has it's own set of drawbacks.

Feedback and Knowledge Base