Feedback by UserVoice

JR

My feedback

  1. 13 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
    JR commented  · 

    Agree with this concern. We all know about the infamous KPMG Teams chat retention issue earlier this year - additional controls, confirmations, alerts (e.g. alerts to all GAs, etc.) for any pending retention policy changes would be a great safeguard addition.

    Immediate GA notification example: "Changes have been made to the Retention Policy for X .. this will take effect in 24 hours .. or you can force it immediately by doing X in powershell... If you want to cancel this retention policy change, do Y."

    JR supported this idea  · 
  2. 325 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    JR supported this idea  · 
  3. 47 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    JR supported this idea  · 
  4. 108 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Delve » Delve for Windows  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    JR commented  · 

    Agree, would be nice to export to excel, csv or ppt - in both Delve or MS Teams org view. This would be a nice end user feature - us tech nerds know how to use posh to pull this information, but a simple export button would be nice for end users.

  5. 65 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General » Users, Photos, Contacts  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    JR commented  · 

    We're beginning to see our users maxing out their Office licenses. When reviewing their license usage, we're seeing a large number of decommissioned computers, or old computers they are no longer using.

    PowerShell: We'd like to run a report of Device Names registered per user, and a way to Deactivate computes programmatically.

    Yes, users can do it themselves, but if we can compare the registered device list against our decommissioned list, we can remove those PCs for the users and cause them one less problem.

    JR supported this idea  · 
  6. 444 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    JR supported this idea  · 
  7. 2,457 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    84 comments  ·  Office 365 Admin » Service Health Dashboard  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    JR commented  · 

    We need this.. at least some posh endpoints we can query.

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

    Voted. This is a big problem. Tenacy restrictions do nothing to prevent users from setting up personal Outlook accounts and leaking data. Outlook GPOs are ineffective because users can just use OWA. Blocking personal OneDrive is possible by blocking specific endpoints, but what a pain.

    AIP doesn't really help since most companies aren't in the position to have all of their sensitive data labeled (yet), and DLP doesn't help because lots of sensitive data can be sent out without trigger DLP rules. I found posts from 2014 complaining of this issue -- for a security minded company like Microsoft, fixing this problem should be way ahead of incremental features.

    JR supported this idea  · 

Feedback and Knowledge Base