> ## Documentation Index
> Fetch the complete documentation index at: https://docs.accessowl.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Microsoft

## Capabilities

<CardGroup cols={2}>
  <Card title="Structure Sync" icon="diagram-project">
    AccessOwl periodically syncs the permissions schema of an application.
  </Card>

  <Card title="User Sync" icon="arrows-rotate">
    AccessOwl periodically syncs a list of users along with their assigned permissions.
  </Card>

  <Card title="Provisioning" icon="user-plus">
    AccessOwl creates or removes user accounts with the specified permissions during access requests or revocations.

    **Note:** Distribution Groups cannot be automatically provisioned or deprovisioned due to API limitations at Microsoft. Only Roles, Licenses, and Security Groups can be managed.
  </Card>

  <Card title="Directory Sync" icon="folder-open">
    AccessOwl syncs (creates, removes, or deactivates) users from directories like Slack, Microsoft365, Okta, or Google into the AccessOwl users database.
  </Card>
</CardGroup>

## FAQ

<AccordionGroup>
  <Accordion title="Does AccessOwl set default mailbox or calendar permissions when provisioning a Microsoft 365 user?">
    No. Microsoft 365 provisioning only creates the account and assigns licenses, Entra directory roles, and group memberships. AccessOwl never sets or changes Exchange mailbox or calendar folder permissions.

    A newly created mailbox keeps Microsoft's own default: the calendar's **Default** permission is set to **AvailabilityOnly** (free/busy). If your organization prefers a different org-wide calendar sharing level, apply it on the Microsoft side, as Exchange does not automatically push an org-wide default onto new mailboxes.
  </Accordion>
</AccordionGroup>