Share via

User Account Notes / hide profile card attribute

Anonymous
2022-03-23T19:14:18+00:00

Is there a way to hide a profile card attribute? At the moment, we are using the Office field to put notes on an account whether the user is a consultant and their end dates and litigation account with other quick notes on an account. However the notes keep showing up on the office field or any other field we use on the Azure Directory. Is there any other way to store account notes that is not visible to users and just visible to the admin? or is there a way to hide a profile card attribute?

Microsoft 365 and Office | Install, redeem, activate | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Anonymous
    2022-03-24T10:17:20+00:00

    Thank you Kelly for replying! The issue we have is that we want to hide a field from the Profile card. We still need the field populated but not visible to users. Is that still possible? Or is there a comments field on Azure Directory we can use?

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-03-23T20:21:33+00:00

    Dear htechdesk ,

    Thanks for choosing Microsoft community!

    I have read your question carefully and done some research, please kindly refer to following:

    On the profile card in Microsoft 365, you can find information about users that is stored and maintained by your organization, for example Job title or Office location.

    Use the profileCardProperty resource to show additional properties from Azure AD on profile cards for an organization, by:

    • Making additional attributes visible
    • Adding custom attributes

    Additional properties will display in the Contact section of the profile card in Microsoft 365.

    You can also delete custom attributes from profile cards of the organization.

    Note

    Operations on the profileCardProperty resource that use delegated permissions require the signed-in user to have a tenant administrator or global administrator role.

    Make additional attributes visible

    You can make the following attributes from Azure Active Directory (Azure AD) visible on users' profile cards. These attributes are not case-sensitive:

    • UserPrincipalName
    • Fax
    • StreetAddress
    • PostalCode
    • StateOrProvince
    • Alias

    The following table shows how the Azure AD attributes correspond with properties of the Microsoft Graph user entity.

    Azure AD attribute User entity property
    UserPrincipalName userPrincipalName
    Fax faxNumber
    StreetAddress streetAddress
    PostalCode postalCode
    StateOrProvince state
    Alias mailNickname

    You can add any of these attributes to the profile card by configuring your organization settings and adding the attribute as the directoryPropertyName property of a profileCardProperty in Microsoft Graph. When you make additional attributes visible, you must use the property names for en-us. You don't have to add localized values. The additional properties will automatically be shown in the language settings that the user has specified for Microsoft 365.

    Important

    When adding an attribute to profile card, it takes up to 24 hours for the addition to be displayed.

    Example

    The following example displays the Alias attribute on the profile card.

    POST https://graph.microsoft.com/beta/organization/{tenantid}/settings/profileCardProperties
    Content-Type: application/json
    
    {
      "directoryPropertyName": "Alias"
    }
    

    If successful, the response returns a 201 OK response code and a profileCardProperty object in the response body. The value for the Alias attribute would be displayed on a user's profile card.

    HTTP/1.1 201 OK
    Content-type: application/json
    
    {
      "directoryPropertyName": "Alias",
      "annotations": []
    }
    

    Adding a custom attribute

    You can add any of the 15 Azure AD custom extension attributes to users' profile cards by configuring your organization settings and adding the corresponding value as a profileCardProperty in Microsoft Graph. You can add one profileCardProperty resource at a time.

    It takes up to 24 hours for the changes to show on profile cards.

    Custom properties are not searchable and can't be used to search for people across Microsoft apps and services.

    The following table shows how the Azure AD custom extension attribute names correspond to the supported values for the directoryPropertyName property of the profileCardProperty resource. These Azure AD custom extension attribute names are not case-sensitive:

    Azure AD custom extension attribute Value to specify as directoryPropertyName
    extensionAttribute1 customAttribute1
    extensionAttribute2 customAttribute2
    extensionAttribute3 customAttribute3
    extensionAttribute4 customAttribute4
    extensionAttribute5 customAttribute5
    extensionAttribute6 customAttribute6
    extensionAttribute7 customAttribute7
    extensionAttribute8 customAttribute8
    extensionAttribute9 customAttribute9
    extensionAttribute10 customAttribute10
    extensionAttribute11 customAttribute11
    extensionAttribute12 customAttribute12
    extensionAttribute13 customAttribute13
    extensionAttribute14 customAttribute14
    extensionAttribute15 customAttribute15

    Example

    The following example adds the first Azure AD custom extension attribute to the profile card, using the display name Cost center. For users that have set their language settings to German, the display name will be Kostenstelle. Request

    POST https://graph.microsoft.com/beta/organization/{tenantid}/settings/profileCardProperties
    Content-Type: application/json
    
    {
      "directoryPropertyName": "customAttribute1",
      "annotations": [
        {
          "displayName": "Cost center",
          "localizations": [
            {
              "languageTag": "de",
              "displayName": "Kostenstelle"
            }
          ]
        }
      ]
    }
    

    If a language is not supported, the property name will be shown with the default value.

    If successful, the response returns a 201 OK response code and a profileCardProperty object in the response body. In this example you can assume that the profile card displays Kostenstelle for all users that have set their language settings to German on the profile card. For all other users, Cost center will be displayed on the profile card. Response

    HTTP/1.1 201 OK
    Content-type: application/json
    
    {
      "directoryPropertyName": "customAttribute1",
      "annotations": [
        {
          "displayName": "Cost center",
          "localizations": [
            {
              "languageTag": "de",
              "displayName": "Kostenstelle"
            }
          ]
        }
      ]
    }
    

    Deleting a custom attribute

    Following the same mapping between Azure AD custom extension attributes and profile card custom attributes (such as customAttribute1) as described in the preceding section Adding a custom attribute, you can delete a custom attribute using the delete operation as shown in the example below:

    Example

    The following example deletes the custom attribute customAttribute5 from the organization settings. A successful deletion returns HTTP 204. Request

    DELETE https://graph.microsoft.com/beta/organization/{organizationId}/settings/profileCardProperties/customAttribute5
    

    Response

    HTTP/1.1 204 No Content
    

    Hope this help you, if there is any deviation in my understanding, please forgive me and provide me with more details. I am more than happy to continue to help you. I wish you all the best!

    Best regards,

    Kerry

    Was this answer helpful?

    0 comments No comments