Enterprise Data Classification

The up you are in the below table more the data restriction applies.

 Data
Classification
 Definition Examples
 Access Control
Data
 Data used to manage access to
administrative roles or sensitive
functions
 Common Examples:
Secrets (passwords,
certificates, encryption keys, storage
keys).
For partner hosted clouds, service
operator owned passwords or
certificates.
 Customer
Content
 This is the data, information and
code that admins, users (if present) provide
to, transfers in, stores in or
process in the ORG online
service or product
 Common Examples:
Customer-owned/ provided secrets
(passwords, certificates, encryption keys,
storage keys, Bring Your Own Key)
Customer generated blob or structured
storage data
Inferences when Customer Content
remains
Machine learning built models with data
that is private/unique to a customer (e.g.
tenant specific dictionaries)
The email addresses and domains of nontenants
Biometric identifiers / datasets
Hashed, and/or Salted+Hashed customer
content (including secrets) remain Customer
Content.

E-mail body or e-mail attachment
IM or Voice Conversations

file body, photos/images uploaded by the
customer, search query strings (user
entered), personal health information (PHI),
personal tax related information
Meeting Location information – Free form text
“Starbucks down by 8th and Main”
Application usage data associated to a tenant
and/ or user .

Table and Column Names, all object names
inside a SQL DB, Topic and Partition Names
(HDInsight Kafka), Schema of the customer
and other customer-named objects below
ARM
 End User
Identifiable
Information
(EUII)
 Data that directly identifies or could be used to identify the authenticated user of an ORG service. EUII does not
contain admin data. EUII d oes not extend to other personal information found in Customer Content (e.g. contact lists are
Customer Content), contact lists are Customer Content).
 Common Examples:
User-specific IP address (IPv4)
Interface ID (last 64 bits of IPv6 address)
User Principal Name
Local-part of e-mail address

E-mail subject line
User name or display name
Office number
Employee ID
Address Book Data
Location Information of a person
(Including Lat/Long)
User’s machine Name
SIP URI
International Mobile Equipment Identifier
(IMEI) or Integrated Circuit Card ID (ICCID)
Inferences if EUII remains
E-mail attachment
name/file name, path information for users’
documents

Behavioral/Usage Data that is linkable to
an individual user
Customer-created AD Data (e.g.,
identities or user names of AD end users)
Customer Global Address List (GAL) Data:
name, office address, phone numbers,
manager/direct reports, job title,
distribution group memberships)
Full browser
fingerprint, unsalted hashed EUII
 Support Data All data provided to ORG by the customer as part of a
customer engagement to obtain support services.
Note: Data accessed by Support personnel within production systems and that remains within
the production system retains its original data classification. Customer Data pulled with a
customer’s consent from
production systems to assist in the resolution of an active support ticket will be classified as Support Data.
Note: Numerical case IDs/ticket IDs generated by ORG and assigned to Support cases are
System Metadata. These IDs are not provided by Customer and do
not contain/are not derived from Support Data provided by Customer. In contrast, case title is provided by Customer or generated by ORG on the
customer’s behalf and is classified
as Support Data.
 • Support requests from customers
and phone conversations, online chat
sessions, or remote assistance
sessions between support
professionals and customers
• Case notes and/or records related to
support requests from customers
• Data provided to ORG by the
customer as part of support activities
 Feedback Data provided as part of a review
or feedback for one of our
products and services that
includes personal data.
Note: Feedback combined with any other data collected from outside of the Feedback user
experience and corresponding to a
higher classification hierarchy, by
operation of the Contamination
Model, becomes encompassed
under the data classification
corresponding to the added data
element (e.g. EUII, EUPI, OII)

• User-initiated feedback, responses to a survey or a review of one of ORG products and services, including any
linked or attached data such as email
addresses, screen shots, attachments or comments (assuming no ability to edit the response once submitted)
• Event-Driven Diagnostic surveys such
as a failure event or a crash following by a dialog asking for additional details, where actual failure events,
crash data and diagnostic data can only be treated as Feedback if it is
collected in an approved Feedback user experience.
• A review and/or rating entered in a product or service where the purpose of the product or service is to capture
and publish reviews and/or ratings
and the end user maintains the ability
to edit the review and/or rating
• Numerical ratings selected by the end
users as part of providing feedback or a review
• Emails or other Customer Data
provided by the end user as part of a Dissatisfaction (DSAT) interaction
• Experience quality surveys
• Content ratings and reviews
• Rate & Review – Survey redirects to additional feedback experiences
• Suggest a Feature
• Upvotes (+1 votes) and replies added to other feedback or forum posts
 Account Data Contact and billing/ purchase/ payment/ license information for the enterprise,
including the admin and any subdelegated admins.
 Customer’s provisioning information Account configuration and billing data Tenant administrator contact information
(e.g. tenant administrator’s name,
address, e-mail address, phone number). Note that contact information
for users other than the tenant admin is EUII. Information about service health of
customer machines and applications, registry data, and error-tracking files. This also includes Licensing and Purchase
Information.
 Public Personal
Data
 Publicly available personal information that ORG obtains from external sources. Public Personal Data is
not Customer Content, EUII, or EUPI since the data was not input
by the customer
 Publicly available information that
identifies a person, including cases where
the person leverages a pseudonym/user
handle/screen name. Social media examples include: Public Tweets,
Facebook posts, YouTube videos, and
Instagram data.
Public LinkedIn data that identifies a person is Public Personal Data
End User
Pseudonymous
Identifiers
(EUPI)
An identifier created by ORG tied to the user of a ORG service. When EUPI is combined with other information
(such as a mapping table), it identifies the end user.
Note that EUPI does not contain information uploaded or created
by the customer (Customer
Content or EUII)
User GUIDs or PUIDs
Other common GUIDs that are EUPI
include: machine IDs, device IDs
Session IDs
Salted Hashed EUII moving outside the
compliance boundary; where the salt
stays within the service’s compliance
boundary
Salted Hashed and Encrypted EUII moving
outside the compliance boundary, where
the keys stay within the service’s
compliance boundary
Organization
Identifiable
Information
(OII)
Data that can be used to identify a particular tenant/
subscription/ deployment/
organization (generally config or
usage data)
Not linkable to a user
Does not contain Customer
Content
Tenant ID (non-GUID)
TenantID (GUID) – due to the existence of many
out of boundary TenantID to name mapping tables
Tenant usage data
Tenant IP Addresses (IPv4) such as
tenant’s firewall IP address
Global Prefix and Subnet ID (first 64 bits
of IPv6 address)
Tenant Domain name in e-mail address

Mapping of organizational GUID to
organization

Aggregated behavioral data associable with a
tenant but not users
Meeting Location: if the location resource is
defined by the tenant from the tenant’s
address book
• Software, systems or container names
created or provided by customers, such as
configuration settings, Account Name (ADL), VM Name, Cluster DNS
Name (HDInsight), SQL Server and Database
Name, Global Database Account Name
(CosmosDB), Machine or Agent Name, Storage
Account Name, Service Name, Form Name,
System
Metadata
Data generated in the course of running the service, not linkable
to a user or tenant. Does not contain Access Control Data,
Customer Content, EUII, Support
Data, Account Data, Public Personal Data, EUPI, or OII.
The following are System Metadata when devoid of Customer Content/Access
Control/EUII/EUPI/OII/Support Data/Account Data/Public Personal Data:
Event Logs
Access Control Logs
Account information belonging to
Microsoft operations personnel
Microsoft server names/server IPs
Behavioral/Usage Data
Server patching and vulnerability data
Service configuration data
Telemetry (on-prem or cloud)

Telecommunication region specific SHORT
CODE phone numbers (e.g. 911)
unique
identifiers tied to end users are now EUPI
Public NonPersonal DataSaaS: Publicly available
information that Microsoft
obtains from external
sources. Does not contain Public
Personal Data.
PaaS: Does not define Public
Non-Personal Data
Weather data
News stories without personal
information
Announcements about corporations (e.g.
earnings data) that don’t include data about individuals

Resolving technical problems:

Solve your technical problems instantly

We provide Remote Technical Support from Monday to Sunday, 7:00PM to 1:00 AM

Mail your problem details at writeulearn@gmail.com along with your mobile numberand we will give you a call for further details. We usually attend your problems within 60 minutes and solve it in maximum 2 days.