Feedback by UserVoice

Microsoft Information Protection (MIP)

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Sensitivte Information Types  ·  Flag idea as inappropriate…  ·  Admin →
  2. Please make clear which set of Sensitive Information Types is applied when

    It is unclear which definitions of the sensitive information types are used.
    There are two webpages which describes those -
    https://docs.microsoft.com/en-us/exchange/policy-and-compliance/data-loss-prevention/sensitive-information-types?view=exchserver-2019#netherlands-citizens-service-bsn-number
    and
    https://docs.microsoft.com/en-us/microsoft-365/compliance/sensitive-information-type-entity-definitions?view=o365-worldwide#netherlands-citizens-service-bsn-number

    I assumed we have the latter one, but it turns out to be the first one. We can tell from the detection of keyword "BSN" and not "bsn".
    Even more confusing: we use the UL client in Office. Testing at the portal (https://protection.office.com/sensitiveTypes) a document containing "bsn / 111222333 / 12-12-2020" the number is detected correctly, however with the same document in Word this sequence is not detected.

    It would be nice if we know…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Sensitivte Information Types  ·  Flag idea as inappropriate…  ·  Admin →
  3. Sensitive Info Types - Test Type Button

    The "Test Type" button is only accessible to Global Admins after a Sensitive Info Type is created. I would like to request that the "Test Type" button be made available to all those authorized at all times, not just available when a Compliance Administrator creates a type for the first time.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Sensitivte Information Types  ·  Flag idea as inappropriate…  ·  Admin →
  4. Encrypt-Only should have a clearer hint for its usage

    The new "Encrypt-Only" built-in feature in Exchange OME is great. However, it will be great and more helpful if it has much clearer hint for its usage. We would like to see something like this: "This message is encrypted and encryption can’t be removed. Recipients can forward this email to anyone and text from the email can be copied and pasted."
    If you look at Do Not Forward feature, it has very clear hint for what the recipient can do and cannot do.
    The reason for this is that our users may not understand clearly that Encrypt-Only can be copied…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Sensitivte Information Types  ·  Flag idea as inappropriate…  ·  Admin →
  5. LDAPS

    enable configure LDAPS for Azure DevOps server, not LDAP

    0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Sensitivte Information Types  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base