+|[Presence](../resources/presence.md)| `/communications/presences/{id}` (single user), `/communications/presences?$filter=id in ('{id}','{id}',…)` (multiple users)|

+## Methods

+| Method | Return Type |Description|

+|:|:--|:-|

+|[Get contact](../api/contact-get.md) | [contact](contact.md) |Read properties and relationships of contact object.|

+|[Create](../api/user-post-contacts.md) | [contact](contact.md) |Add a contact to the root Contacts folder or to the contacts endpoint of another contact folder.|

+|[Update](../api/contact-update.md) | [contact](contact.md) |Update contact object. |

+|[Delete](../api/contact-delete.md) | None |Delete contact object. |

+|[delta](../api/contact-delta.md)|[contact](contact.md) collection| Get a set of contacts that have been added, deleted, or updated in a specified folder.|

+|**Open extensions**| | |

+|[Create open extension](../api/opentypeextension-post-opentypeextension.md) |[openTypeExtension](opentypeextension.md)| Create an open extension and add custom properties to a new or existing resource.|

+|[Get open extension](../api/opentypeextension-get.md) |[openTypeExtension](opentypeextension.md) collection| Get an open extension identified by the extension name.|

+|**Schema extensions**| | |

+|[Add schema extension values](/graph/extensibility-schema-groups) || Create a schema extension definition and then use it to add custom typed data to a resource.|

+|**Extended properties**| | |

+|[Create single-value extended property](../api/singlevaluelegacyextendedproperty-post-singlevalueextendedproperties.md) |[contact](contact.md) |Create one or more single-value extended properties in a new or existing contact. |

+|[Get contact with single-value extended property](../api/singlevaluelegacyextendedproperty-get.md) | [contact](contact.md) | Get contacts that contain a single-value extended property by using `$expand` or `$filter`. |

+|[Create multi-value extended property](../api/multivaluelegacyextendedproperty-post-multivalueextendedproperties.md) | [contact](contact.md) | Create one or more multi-value extended properties in a new or existing contact. |

+|[Get contact with multi-value extended property](../api/multivaluelegacyextendedproperty-get.md) | [contact](contact.md) | Get a contact that contains a multi-value extended property by using `$expand`. |

+## Properties

+| Property | Type |Description|

+|:|:--|:-|

+|assistantName|String|The name of the contact's assistant.|

+|birthday|DateTimeOffset|The contact's birthday. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is `2014-01-01T00:00:00Z`|

+|categories|String collection|The categories associated with the contact. Each category corresponds to the **displayName** property of an [outlookCategory](outlookcategory.md) defined for the user.|

+|changeKey|String|Identifies the version of the contact. Every time the contact is changed, ChangeKey changes as well. This allows Exchange to apply changes to the correct version of the object.|

+|children|String collection|The names of the contact's children.|

+|companyName|String|The name of the contact's company.|

+|createdDateTime|DateTimeOffset|The time the contact was created. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is `2014-01-01T00:00:00Z`|

+|department|String|The contact's department.|

+|displayName|String|The contact's display name. You can specify the display name in a [create](../api/user-post-contacts.md) or [update](../api/contact-update.md) operation. Note that later updates to other properties may cause an automatically generated value to overwrite the displayName value you have specified. To preserve a pre-existing value, always include it as displayName in an [update](../api/contact-update.md) operation.|

+|emailAddresses|[typedEmailAddress](typedemailaddress.md) collection|The contact's email addresses.|

+|fileAs|String|The name the contact is filed under.|

+|flag|[followupFlag](followupflag.md)|The flag value that indicates the status, start date, due date, or completion date for the contact. |

+|gender |String |The contact's gender. |

+|generation|String|The contact's generation.|

+|givenName|String|The contact's given name.|

+|id|String| Unique identifier for the contact. [!INCLUDE [outlook-beta-id](../../includes/outlook-immutable-id.md)] Read-only. |

+|imAddresses|String collection|The contact's instant messaging (IM) addresses.|

+|initials|String|The contact's initials.|

+|jobTitle|String|The contactΓÇÖs job title.|

+|lastModifiedDateTime|DateTimeOffset|The time the contact was modified. The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is `2014-01-01T00:00:00Z`|

+|manager|String|The name of the contact's manager.

+|middleName|String|The contact's middle name.|

+|nickName|String|The contact's nickname.|

+|officeLocation|String|The location of the contact's office.|

+|parentFolderId|String|The ID of the contact's parent folder.|

+|personalNotes|String|The user's notes about the contact.|

+|phones |[phone](phone.md) collection |Phone numbers associated with the contact, for example, home phone, mobile phone, and business phone. |

+|postalAddresses |[physicalAddress](physicaladdress.md) collection |Addresses associated with the contact, for example, home address and business address. |

+|profession|String|The contact's profession.|

+|spouseName|String|The name of the contact's spouse/partner.|

+|surname|String|The contact's surname.|

+|title|String|The contact's title.|

+|websites |[website](website.md) collection|Web sites associated with the contact. |

+|weddingAnniversary |Date |The contact's wedding anniversary. |

+|yomiCompanyName|String|The phonetic Japanese company name of the contact.|

+|yomiGivenName|String|The phonetic Japanese given name (first name) of the contact.|

+|yomiSurname|String|The phonetic Japanese surname (last name) of the contact.|

+## Relationships

+| Relationship | Type |Description|

+|:|:--|:-|

+|extensions|[extension](extension.md) collection|The collection of open extensions defined for the contact. Nullable.|

+|multiValueExtendedProperties|[multiValueLegacyExtendedProperty](multivaluelegacyextendedproperty.md) collection| The collection of multi-value extended properties defined for the contact. Read-only. Nullable.|

+|photo|[photo](profilephoto.md)| Optional contact picture. You can get or set a photo for a contact.|

+|singleValueExtendedProperties|[singleValueLegacyExtendedProperty](singlevaluelegacyextendedproperty.md) collection| The collection of single-value extended properties defined for the contact. Read-only. Nullable.|

+The following is a JSON representation of the resource.

+Represents an organizational contact. Organizational contacts are managed by an organization's administrators and are different from [personal contacts](contact.md). Additionally, organizational contacts are either synchronized from on-premises directories or from Exchange Online, and are read-only in Microsoft Graph.

+| **Organizational contacts** |

+| **Organizational hierarchy** |

+| proxyAddresses | String collection | For example: `["SMTP: bob@contoso.com", "smtp: bob@sales.contoso.com"]`. Changes to the **mail** property will also update this collection to include the value as an SMTP address. For more information, see [mail and proxyAddresses properties](#mail-and-proxyaddresses-properties). The proxy address prefixed with `SMTP` (capitalized) is the primary proxy address while those prefixed with `smtp` are the secondary proxy addresses. For Azure AD B2C accounts, this property has a limit of ten unique addresses. Read-only in Microsoft Graph; you can update this property only through the [Microsoft 365 admin center](/exchange/recipients-in-exchange-online/manage-user-mailboxes/add-or-remove-email-addresses). Not nullable. <br><br>Supports `$filter` (`eq`, `not`, `ge`, `le`, `startsWith`). |

+### mail and proxyAddresses properties

+**mail** and **proxyAddresses** are both email-related properties. **proxyAddresses** is a collection of addresses only relevant for Microsoft Exchange server. It's used to store a list of mail addresses for a user that are tied to a single mailbox. **mail** property is used as the user's email address for various purposes including user sign in and defines the primary proxy address.

+

+Both **mail** and **proxyAddresses** can be retrieved through the [GET user](add link) API on MS Graph. **mail** can be updated via the [PATCH method of the Update user](add link) API, but **proxyAddresses** can't be updated via Microsoft Graph. When a user's **mail** property is updated, it triggers recalculation of **proxyAddresses** and the newly updated mail is set to be the primary proxy address, except in the following scenarios:

+

+1. If a user has a license that includes Microsoft Exchange, all their proxy addresses must belong to a verified domain on the tenant. Any that don't belong to verified domains are silently removed.

+2. A user's mail will NOT be set to the primary proxy address if the user is a guest and the primary proxy address contains the guest user UPN string with #EXT#.

+3. A user's mail will NOT be removed, even if they no longer have proxy addresses, if the user is a guest.

+

+**proxyAddresses** are unique across directory objects (users, groups, and organizational contacts). If a user's **mail** property conflicts with one of the **proxyAddresses** of another object, you'll successfully update the **mail** property; however, the new mail value won't be added to the **proxyAddresses** collection.

+POST /solutions/bookingBusinesses/{id}/appointments/{id}/cancel

+DELETE /solutions/bookingBusinesses/{id}/appointments/{id}

+GET /solutions/bookingBusinesses/{id}/appointments/{id}

+PATCH /solutions/bookingBusinesses/{id}/appointments/{id}

+DELETE /solutions/bookingBusinesses/{id}

+GET /solutions/bookingBusinesses/{id}

+GET /solutions/bookingBusinesses/{id}/appointments

+GET /solutions/bookingBusinesses/{id}/calendarView?start={start-value}&end={end-value}

+GET /solutions/bookingBusinesses/{id}/customers

+GET /solutions/bookingBusinesses/{bookingBusinessesId}/customQuestions

+GET /solutions/bookingBusinesses/{id}/services

+GET /solutions/bookingBusinesses/{id}/staffMembers

+GET /solutions/bookingBusinesses

+POST /solutions/bookingBusinesses/{id}/appointments

+POST /solutions/bookingBusinesses

+POST /solutions/bookingBusinesses/{id}/customers

+POST /solutions/bookingBusinesses/{bookingBusinessesId}/customQuestions

+POST /solutions/bookingBusinesses/{id}/services

+POST /solutions/bookingBusinesses/{id}/staffMembers

+POST /solutions/bookingBusinesses/{id}/publish

+POST /solutions/bookingBusinesses/{id}/unpublish

+PATCH /solutions/bookingBusinesses/{id}

+GET /solutions/bookingCurrencies/{id}

+GET /solutions/bookingCurrencies

+DELETE /solutions/bookingBusinesses/{id}/customers/{id}

+GET /solutions/bookingBusinesses/{id}/customers/{id}

+PATCH /solutions/bookingBusinesses/{id}/customers/{id}

+DELETE /solutions/bookingBusinesses/{bookingBusinessesId}/customQuestions/{bookingCustomQuestionId}

+GET /solutions/bookingBusinesses/{bookingBusinessesId}/customQuestions/{bookingCustomQuestionId}

+PATCH /solutions/bookingBusinesses/{bookingBusinessesId}/customQuestions/{bookingCustomQuestionId}

+DELETE /solutions/bookingBusinesses/{id}/services/{id}

+GET /solutions/bookingBusinesses/{id}/services/{id}

+PATCH /solutions/bookingBusinesses/{id}/services/{id}

+DELETE /solutions/bookingBusinesses/{id}/staffMembers/{id}

+GET /solutions/bookingBusinesses/{id}/staffMembers/{id}

+PATCH /solutions/bookingBusinesses/{id}/staffMembers/{id}

+|[Presence](../resources/presence.md)| `/communications/presences/{id}` (single user), `/communications/presences?$filter=id in ('{id}','{id}',…)` (multiple users)|

+The following is a JSON representation of the resource.

+Represents an organizational contact. Organizational contacts are managed by an organization's administrators and are different from [personal contacts](contact.md). Additionally, organizational contacts are either synchronized from on-premises directories or from Exchange Online, and are read-only in Microsoft Graph.

+| **Organizational contacts** |

+| **Organizational hierarchy** |

+|proxyAddresses|String collection|For example: `["SMTP: bob@contoso.com", "smtp: bob@sales.contoso.com"]`. Changes to the **mail** property will also update this collection to include the value as an SMTP address. For more information, see [mail and proxyAddresses properties](#mail-and-proxyaddresses-properties). The proxy address prefixed with `SMTP` (capitalized) is the primary proxy address while those prefixed with `smtp` are the secondary proxy addresses. For Azure AD B2C accounts, this property has a limit of ten unique addresses. Read-only in Microsoft Graph; you can update this property only through the [Microsoft 365 admin center](/exchange/recipients-in-exchange-online/manage-user-mailboxes/add-or-remove-email-addresses). Not nullable. <br><br>Returned only on `$select`. Supports `$filter` (`eq`, `not`, `ge`, `le`, `startsWith`).|

+### mail and proxyAddresses properties

+**mail** and **proxyAddresses** are both email-related properties. **proxyAddresses** is a collection of addresses only relevant for Microsoft Exchange server. It's used to store a list of mail addresses for a user that are tied to a single mailbox. **mail** property is used as the user's email address for various purposes including user sign in and defines the primary proxy address.

+

+Both **mail** and **proxyAddresses** can be retrieved through the [GET user](add link) API on MS Graph. **mail** can be updated via the [PATCH method of the Update user](add link) API, but **proxyAddresses** can't be updated via Microsoft Graph. When a user's **mail** property is updated, it triggers recalculation of **proxyAddresses** and the newly updated mail is set to be the primary proxy address, except in the following scenarios:

+

+1. If a user has a license that includes Microsoft Exchange, all their proxy addresses must belong to a verified domain on the tenant. Any that don't belong to verified domains are silently removed.

+2. A user's mail will NOT be set to the primary proxy address if the user is a guest and the primary proxy address contains the guest user UPN string with #EXT#.

+3. A user's mail will NOT be removed, even if they no longer have proxy addresses, if the user is a guest.

+

+**proxyAddresses** are unique across directory objects (users, groups, and organizational contacts). If a user's **mail** property conflicts with one of the **proxyAddresses** of another object, you'll successfully update the **mail** property; however, the new mail value won't be added to the **proxyAddresses** collection.

+ - name: List

+ - name: Get

+ - name: Get delta