Privacy changes to Microsoft 365 Usage Analytics

Published Aug 30 2021 09:00 AM 8,402 Views
Microsoft

At Microsoft, we’re committed to both data-driven insights and user privacy. As part of that commitment, we’re making a change to Microsoft 365 usage analytics on September 1st to pseudonymize user-level information by default. This change affects the following products and APIs, and will help companies support their local privacy laws: 

 

Global administrators can revert this change for their tenant and show identifiable user information if their organization’s privacy practices allow. This can be achieved in the Microsoft 365 admin center by going to Settings > Org Settings > Services and selecting Reports. Under Choose how to show user information, uncheck the statement In all reports, display de-identified names for users, groups, and sites, and then save your changes. Showing identifiable user information is a logged event in the Microsoft 365 compliance center audit log.  

 

When user identification is enabled, administrative roles and the report reader role will be able to see identifiable user level information. Global reader and Usage Summary Reports Reader roles will not have access to identifiable user information, regardless of the setting chosen. 

 

These changes to the product will bolster privacy for users while still enabling IT professionals to measure adoption trends, track license allocation and determine license renewal in Microsoft 365. 

 

Continue the conversation by joining us in the Microsoft 365 Tech Community! Whether you have product questions or just want to stay informed with the latest updates on new releases, tools, and blogs, Microsoft 365 Tech Community is your go-to resource to stay connected!

14 Comments
Occasional Visitor

Bonjour,

Depuis que cette fonctionnalité a été activée, nous avons une série de chiffres et de lettres à la place des username.

Par contre, dans les paramètres de l'organisation > Rapports, l'option est bien cochée.

En décochant l'option "Show identifiable user information in reports", on retrouve bien les noms ou adresses mails dans les rapports.

Il y a soit un problème de traduction, soit un problème de fonctionnalité.

Merci d'avance

Senior Member

Hi,

 

was this information communicated in advance via some other location? Without such communication, applications dependent on the previous behavior and setting are suddenly broken, requiring customer to react.

 

Rob O

Frequent Visitor

There is some way to decode the pseudonymize data? there are some graph endpoint to recover the user information?

New Contributor

@EmanuelVazquez 

Yes : 

Global administrators can revert this change for their tenant and view identifiable user information if their organization's privacy practices permit. 
This can be done in the Microsoft 365 admin center by going to Settings> Organization Settings> Services and selecting Reports.
Under Choose how to display user information, deselect Display identifiable user information in reports.
 
New Contributor

Is it possible to get the same kind of pseudonymization on other graph endpoints?

 

It would be great to be able to tie data to departments or countries (not necessarily individual users) by combining the data with https://graph.microsoft.com/v1.0/users.

Regular Visitor

Was this announced in the M365 or Azure Admin Message Center? There is also nothing about anonymizing usage data in the M365 Road Map, other than a reference to Teams usage anonymization in May 2021. Please share where this was announced or communicated prior to August 30th 2021 for a Sept. 1 2021 implementation. This change broke several reports in our environment that require user information to be in the report. We have reverted, but would have appreciated advanced communication. Thank you!

Microsoft

@downtownmtb-Allina @Robert Osborne Thank you for taking the time to share the impact this change has had. This change was announced via the Microsoft 365 public roadmap and message center in the Microsoft 365 Admin Center. The announcement was provided with 30 days notice in line with our standard notification procedures for this type of change.

 

@Axel Andersen I’m not aware of any further efforts regarding pseudonymization for other graph endpoints, we will provide your request to the Graph API team and ask them to reach out.

Senior Member

@James_Bell please can you share the relevant items?

I can only see roadmap feature ID 70774 last modified in June, which refers to admins "will have the option" to anonymise, not that it would be switched to on by default.

The Message Center does not have anything relevant against searches for "privacy", "anonymize", "anonymous".

 

Microsoft

Hi @Simon Gardner , it was contained in Message Center Post: MC275344 and Roadmap ID: 81959

 

Occasional Visitor

You need to update the documentation of the affected methods to indicate that some fields will be anonymized.

 

Ex.  https://docs.microsoft.com/en-us/graph/api/reportroot-getemailactivityuserdetail?view=graph-rest-1.0

Microsoft

Hi @Grattle , thanks for letting me know. I'll work with our documentation team to have the content updated. 

Frequent Visitor

Hi, I want to maintain pseudonymize option in the tenant, but I need to get a report from Graph, anybody knows if there are some way to "decrypt" these data on my side by coding? i'm using c#

Occasional Visitor

Hi, If userPrincipalName and displayName is concealed, how can we know the data belongs to which user? For example, if we want active users report, we can only see the ID which serves no purpose in that report. I understand that we can disable this option, but my question is why do we had this option in the first place?

 

Is there a mapping for the concealed information and the actual information anywhere that only admins can view/fetch? If so, that would be useful.

Microsoft

@EmanuelVazquez we do not provide the ability to decrypt the information.  @Manikandan_N , we include the option to bolster privacy for users while still enabling IT professionals to measure adoption trends, track license allocation and determine license renewal in Microsoft 365.  There is no mapping between the settings.  The change described in the article is to modify the default setting to hide user level information from 'off' to 'on'. We did not modify the functionality of the product with this change, just the default setting which can be reverted using the method described above. 

 

 

%3CLINGO-SUB%20id%3D%22lingo-sub-2717461%22%20slang%3D%22en-US%22%3ERe%3A%20Privacy%20changes%20to%20Microsoft%20365%20Usage%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2717461%22%20slang%3D%22en-US%22%3E%3CP%3EBonjour%2C%3C%2FP%3E%3CP%3EDepuis%20que%20cette%20fonctionnalit%C3%A9%20a%20%C3%A9t%C3%A9%20activ%C3%A9e%2C%20nous%20avons%20une%20s%C3%A9rie%20de%20chiffres%20et%20de%20lettres%20%C3%A0%20la%20place%20des%20username.%3C%2FP%3E%3CP%3EPar%20contre%2C%20dans%20les%20param%C3%A8tres%20de%20l'organisation%20%26gt%3B%20Rapports%2C%20l'option%20est%20bien%20coch%C3%A9e.%3C%2FP%3E%3CP%3EEn%20%3CSTRONG%3Ed%C3%A9cochant%3C%2FSTRONG%3E%20l'option%20%22%3CSTRONG%3EShow%20identifiable%20user%20information%20in%26nbsp%3Breports%3C%2FSTRONG%3E%22%2C%20on%20retrouve%20bien%20les%20noms%20ou%20adresses%20mails%20dans%20les%20rapports.%3C%2FP%3E%3CP%3EIl%20y%20a%20soit%20un%20probl%C3%A8me%20de%20traduction%2C%20soit%20un%20probl%C3%A8me%20de%20fonctionnalit%C3%A9.%3C%2FP%3E%3CP%3EMerci%20d'avance%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2729586%22%20slang%3D%22en-US%22%3ERe%3A%20Privacy%20changes%20to%20Microsoft%20365%20Usage%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2729586%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewas%20this%20information%20communicated%20in%20advance%20via%20some%20other%20location%3F%20Without%20such%20communication%2C%20applications%20dependent%20on%20the%20previous%20behavior%20and%20setting%20are%20suddenly%20broken%2C%20requiring%20customer%20to%20react.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERob%20O%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2730288%22%20slang%3D%22en-US%22%3ERe%3A%20Privacy%20changes%20to%20Microsoft%20365%20Usage%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2730288%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20is%20some%20way%20to%20decode%20the%26nbsp%3B%3CSPAN%3Epseudonymize%20data%3F%20there%20are%20some%20graph%20endpoint%20to%20recover%20the%20user%20information%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2735240%22%20slang%3D%22fr-FR%22%3ERe%3A%20Privacy%20changes%20to%20Microsoft%20365%20Usage%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2735240%22%20slang%3D%22fr-FR%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1149302%22%20target%3D%22_blank%22%3E%40EmanuelVazquez%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%3A%3C%2FP%3E%3CPRE%3E%3CSPAN%20class%3D%22Y2IQFc%22%3EGlobal%20administrators%20can%20revert%20this%20change%20for%20their%20tenant%20and%20view%20identifiable%20user%20information%20if%20their%20organization's%20privacy%20practices%20permit.%20%3CBR%20%2F%3EThis%20can%20be%20done%20in%20the%20Microsoft%20365%20admin%20center%20by%20going%20to%20Settings%26gt%3B%20Organization%20Settings%26gt%3B%20Services%20and%20selecting%20Reports.%20%3CBR%20%2F%3EUnder%20Choose%20how%20to%20display%20user%20information%2C%20deselect%20Display%20identifiable%20user%20information%20in%20reports.%3C%2FSPAN%3E%26nbsp%3B%3C%2FPRE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2735509%22%20slang%3D%22en-US%22%3ERe%3A%20Privacy%20changes%20to%20Microsoft%20365%20Usage%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2735509%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20it%20possible%20to%20get%20the%20same%20kind%20of%20pseudonymization%20on%20other%20graph%20endpoints%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20would%20be%20great%20to%20be%20able%20to%20tie%20data%20to%20departments%20or%20countries%20(not%20necessarily%20individual%20users)%20by%20combining%20the%20data%20with%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgraph.microsoft.com%2Fv1.0%2Fusers%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgraph.microsoft.com%2Fv1.0%2Fusers%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2694137%22%20slang%3D%22en-US%22%3EPrivacy%20changes%20to%20Microsoft%20365%20Usage%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2694137%22%20slang%3D%22en-US%22%3E%3CP%3EAt%20Microsoft%2C%20we%E2%80%99re%20committed%20to%20both%20data-driven%20insights%20and%20user%20privacy.%20As%20part%20of%20that%20commitment%2C%20we%E2%80%99re%20making%20a%20change%20to%20Microsoft%20365%20usage%20analytics%20on%20September%201st%26nbsp%3Bto%20pseudonymize%20user-level%20information%20by%20default.%20This%20change%20affects%26nbsp%3Bthe%20following%20products%20and%20APIs%2C%20and%20will%20help%20companies%20support%20their%20local%26nbsp%3Bprivacy%20laws%3A%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%20data-leveltext%3D%22%EF%82%B7%22%20data-font%3D%22Symbol%22%20data-listid%3D%221%22%20data-aria-posinset%3D%221%22%20data-aria-level%3D%221%22%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fadmin%2Factivity-reports%2Factivity-reports%3Fview%3Do365-worldwide%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMicrosoft%20365%20Reports%20in%20the%26nbsp%3BMicrosoft%20365%26nbsp%3Badmin%20center%3C%2FA%3E%26nbsp%3B%3C%2FLI%3E%0A%3CLI%20data-leveltext%3D%22%EF%82%B7%22%20data-font%3D%22Symbol%22%20data-listid%3D%221%22%20data-aria-posinset%3D%222%22%20data-aria-level%3D%221%22%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fgraph%2Fapi%2Fresources%2Freport%3Fview%3Dgraph-rest-1.0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMicrosoft%20365%20usage%20reports%20in%20Microsoft%20Graph%3C%2FA%3E%26nbsp%3B%3C%2FLI%3E%0A%3CLI%20data-leveltext%3D%22%EF%82%B7%22%20data-font%3D%22Symbol%22%20data-listid%3D%221%22%20data-aria-posinset%3D%223%22%20data-aria-level%3D%221%22%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fteams-analytics-and-reports%2Fteams-reporting-reference%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMicrosoft%20Teams%20analytics%20and%20reporting%3C%2FA%3E%26nbsp%3Bin%20the%20Microsoft%20Teams%20admin%20center%26nbsp%3B%3C%2FLI%3E%0A%3CLI%20data-leveltext%3D%22%EF%82%B7%22%20data-font%3D%22Symbol%22%20data-listid%3D%221%22%20data-aria-posinset%3D%223%22%20data-aria-level%3D%221%22%3EThe%26nbsp%3BreportRoot%3A%26nbsp%3BgetSharePointSiteUsageDetail%26nbsp%3BAPI%20(%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252Fgraph%252Fapi%252Freportroot-getsharepointsiteusagedetail%253Fview%253Dgraph-rest-1.0%26amp%3Bdata%3D04%257C01%257CJames.Bell%2540microsoft.com%257C0c64cee0adba420dcca808d96862aaed%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C637655595288810795%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C1000%26amp%3Bsdata%3Dhr46pIM4MKBLwQuPtx4VdjrVEvpoVn6i36EpYrunpFU%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3E1.0%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252Fgraph%252Fapi%252Freportroot-getsharepointsiteusagedetail%253Fview%253Dgraph-rest-beta%26amp%3Bdata%3D04%257C01%257CJames.Bell%2540microsoft.com%257C0c64cee0adba420dcca808d96862aaed%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C637655595288820748%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C1000%26amp%3Bsdata%3DrFxEpGKknq7e0k5tjEh%252FFexHkA3iDkT1sc%252BM7Z6jhtM%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ebeta%3C%2FA%3E)%20for%20SharePoint%20site%20detail%26nbsp%3B%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EGlobal%20administrators%20can%20revert%20this%20change%20for%20their%20tenant%26nbsp%3Band%20show%20identifiable%20user%20information%20if%20their%20organization%E2%80%99s%20privacy%20practices%20allow.%20This%20can%20be%20achieved%20in%20the%20Microsoft%20365%20admin%20center%20by%20going%20to%20%3CSTRONG%3ESettings%26nbsp%3B%26gt%3B%20Org%20Settings%20%26gt%3B%20Services%3C%2FSTRONG%3E%26nbsp%3Band%20selecting%20%3CSTRONG%3EReports%3C%2FSTRONG%3E.%20Under%20%3CSTRONG%3EChoose%20how%20to%20show%20user%20information%3C%2FSTRONG%3E%2C%20uncheck%20the%20statement%26nbsp%3B%3CSTRONG%3EIn%20all%20reports%2C%20display%20de-identified%20names%20for%20users%2C%20groups%2C%20and%20sites%2C%3C%2FSTRONG%3E%20and%20then%20save%20your%20changes.%26nbsp%3BShowing%20identifiable%20user%20information%20is%20a%20logged%20event%20in%20the%20Microsoft%20365%20compliance%20center%20audit%20log.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20user%20identification%20is%20enabled%2C%20administrative%20roles%20and%20the%20report%20reader%20role%20will%20be%20able%20to%20see%20identifiable%20user%20level%20information.%20Global%20reader%20and%20Usage%20Summary%20Reports%20Reader%20roles%20will%20not%20have%20access%20to%20identifiable%20user%20information%2C%20regardless%20of%20the%20setting%20chosen.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThese%20changes%20to%20the%20product%20will%20bolster%20privacy%20for%20users%20while%20still%20enabling%20IT%20professionals%20to%20measure%20adoption%20trends%2C%20track%20license%20allocation%20and%26nbsp%3Bdetermine%26nbsp%3Blicense%20renewal%20in%20Microsoft%20365.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EContinue%20the%20conversation%20by%20joining%20us%20in%20the%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fcommunity%2Fmicrosoft365%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMicrosoft%20365%20Tech%20Community!%3C%2FA%3E%20Whether%20you%20have%20product%20questions%20or%20just%20want%20to%20stay%20informed%20with%20the%20latest%20updates%20on%20new%20releases%2C%20tools%2C%20and%20blogs%2C%20Microsoft%20365%20Tech%20Community%20is%20your%20go-to%20resource%20to%20stay%20connected!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2694137%22%20slang%3D%22en-US%22%3E%3CP%3ELearn%20more%20about%20a%20change%20coming%20soon%20to%26nbsp%3BMicrosoft%20365%20usage%20analytics!%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2694137%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Graph%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2771911%22%20slang%3D%22en-US%22%3ERe%3A%20Privacy%20changes%20to%20Microsoft%20365%20Usage%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2771911%22%20slang%3D%22en-US%22%3E%3CP%3EWas%20this%20announced%20in%20the%20M365%20or%20Azure%20Admin%20Message%20Center%3F%20There%20is%20also%20nothing%20about%20anonymizing%20usage%20data%20in%20the%20M365%20Road%20Map%2C%20other%20than%20a%20reference%20to%20Teams%20usage%20anonymization%20in%20May%202021.%20Please%20share%20where%20this%20was%20announced%20or%20communicated%20prior%20to%20August%2030th%202021%20for%20a%20Sept.%201%202021%20implementation.%20This%20change%20broke%20several%20reports%20in%20our%20environment%20that%20require%20user%20information%20to%20be%20in%20the%20report.%20We%20have%20reverted%2C%20but%20would%20have%20appreciated%20advanced%20communication.%20Thank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2775814%22%20slang%3D%22en-US%22%3ERe%3A%20Privacy%20changes%20to%20Microsoft%20365%20Usage%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2775814%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1144659%22%20target%3D%22_blank%22%3E%40downtownmtb-Allina%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F144733%22%20target%3D%22_blank%22%3E%40Robert%20Osborne%3C%2FA%3E%26nbsp%3BThank%20you%20for%20taking%20the%20time%20to%20share%20the%20impact%20this%20change%20has%20had.%20This%20change%20was%20announced%20via%20the%20Microsoft%20365%20public%20roadmap%20and%20message%20center%20in%20the%20Microsoft%20365%20Admin%20Center.%20The%20announcement%20was%20provided%20with%2030%20days%20notice%20in%20line%20with%20our%20standard%20notification%20procedures%20for%20this%20type%20of%20change.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F124754%22%20target%3D%22_blank%22%3E%40Axel%20Andersen%3C%2FA%3E%26nbsp%3BI%E2%80%99m%20not%20aware%20of%20any%20further%20efforts%20regarding%20pseudonymization%20for%20other%20graph%20endpoints%2C%20we%20will%20provide%20your%20request%20to%20the%20Graph%20API%20team%20and%20ask%20them%20to%20reach%20out.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2779293%22%20slang%3D%22en-US%22%3ERe%3A%20Privacy%20changes%20to%20Microsoft%20365%20Usage%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2779293%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F291039%22%20target%3D%22_blank%22%3E%40James_Bell%3C%2FA%3E%26nbsp%3Bplease%20can%20you%20share%20the%20relevant%20items%3F%3CBR%20%2F%3E%3CBR%20%2F%3EI%20can%20only%20see%20roadmap%20feature%20ID%26nbsp%3B%3CSPAN%3E70774%20last%20modified%20in%20June%2C%20which%20refers%20to%20admins%20%22will%20have%20the%20option%22%20to%20anonymise%2C%20not%20that%20it%20would%20be%20switched%20to%20on%20by%20default.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20Message%20Center%20does%20not%20have%20anything%20relevant%20against%20searches%20for%20%22privacy%22%2C%20%22anonymize%22%2C%20%22anonymous%22.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2779637%22%20slang%3D%22en-US%22%3ERe%3A%20Privacy%20changes%20to%20Microsoft%20365%20Usage%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2779637%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F41281%22%20target%3D%22_blank%22%3E%40Simon%20Gardner%3C%2FA%3E%26nbsp%3B%2C%20it%20was%20contained%20in%20Message%20Center%20Post%3A%20MC275344%20and%26nbsp%3BRoadmap%20ID%3A%2081959%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2818887%22%20slang%3D%22en-US%22%3ERe%3A%20Privacy%20changes%20to%20Microsoft%20365%20Usage%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2818887%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20need%20to%20update%20the%20documentation%20of%20the%20effected%20methods%20to%20indicate%20that%20some%20fields%20will%20be%20anonymized.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEx.%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fgraph%2Fapi%2Freportroot-getemailactivityuserdetail%3Fview%3Dgraph-rest-1.0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fgraph%2Fapi%2Freportroot-getemailactivityuserdetail%3Fview%3Dgraph-rest-1.0%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2820459%22%20slang%3D%22en-US%22%3ERe%3A%20Privacy%20changes%20to%20Microsoft%20365%20Usage%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2820459%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1177481%22%20target%3D%22_blank%22%3E%40Grattle%3C%2FA%3E%26nbsp%3B%2C%20thanks%20for%20letting%20me%20know.%20I'll%20work%20with%20our%20documentation%20team%20to%20have%20the%20content%20updated.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2822662%22%20slang%3D%22en-US%22%3ERe%3A%20Privacy%20changes%20to%20Microsoft%20365%20Usage%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2822662%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I%20want%20to%20maintain%26nbsp%3B%3CSPAN%3Epseudonymize%20option%20in%20the%20tenant%2C%20but%20I%20need%20to%20get%20a%20report%20from%20Graph%2C%20anybody%20knows%20if%20there%20are%20some%20way%20to%20%22decrypt%22%20these%20data%20on%20my%20side%20by%20coding%3F%20i'm%20using%20c%23%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2835267%22%20slang%3D%22en-US%22%3ERe%3A%20Privacy%20changes%20to%20Microsoft%20365%20Usage%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2835267%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20If%20userPrincipalName%20and%20displayName%20is%20concealed%2C%20how%20can%20we%20know%20the%20data%20belongs%20to%20which%20user%3F%20For%20example%2C%20if%20we%20want%20active%20users%20report%2C%20we%20can%20only%20see%20the%20ID%20which%20serves%20no%20purpose%20in%20that%20report.%20I%20understand%20that%20we%20can%20disable%20this%20option%2C%20but%20my%20question%20is%20why%20do%20we%20had%20this%20option%20in%20the%20first%20place%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20mapping%20for%20the%20concealed%20information%20and%20the%20actual%20information%20anywhere%20that%20only%20admins%20can%20view%2Ffetch%3F%20If%20so%2C%20that%20would%20be%20useful.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2835891%22%20slang%3D%22en-US%22%3ERe%3A%20Privacy%20changes%20to%20Microsoft%20365%20Usage%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2835891%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1149302%22%20target%3D%22_blank%22%3E%40EmanuelVazquez%3C%2FA%3E%26nbsp%3Bwe%20do%20not%20provide%20the%20ability%20to%20decrypt%20the%20information.%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1182391%22%20target%3D%22_blank%22%3E%40Manikandan_N%3C%2FA%3E%26nbsp%3B%2C%20we%20include%20the%20option%26nbsp%3B%3CSPAN%3Eto%20bolster%20privacy%20for%20users%20while%20still%20enabling%20IT%20professionals%20to%20measure%20adoption%20trends%2C%20track%20license%20allocation%20and%26nbsp%3Bdetermine%26nbsp%3Blicense%20renewal%20in%20Microsoft%20365.%26nbsp%3B%3C%2FSPAN%3E%26nbsp%3BThere%20is%20no%20mapping%20between%20the%20settings.%26nbsp%3B%20The%20change%20described%20in%20the%20article%20is%20to%20modify%20the%20default%20setting%20to%20hide%20user%20level%20information%20from%20'off'%20to%20'on'.%20We%20did%20not%20modify%20the%20functionality%20of%20the%20product%20with%20this%20change%2C%20just%20the%20default%20setting%20which%20can%20be%20reverted%20using%20the%20method%20described%20above.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Co-Authors
Version history
Last update:
‎Sep 14 2021 09:31 AM
Updated by: