Send a fax with Microsoft 365

Send a fax with Microsoft 365 is used for moving an Office document into the Faxoryn send workflow. It should not remove the review step or obscure the final delivery state.

Use the least access the connection needs, confirm the supported file and event behavior, and keep a local upload or workspace fallback for carrier outages.

This page covers office, 365. Check the relevant account setting or fax record before you continue.

• Confirm the account and permission scope used by Send a fax with Microsoft 365.
• Review imported files before sending them.
• Keep the Faxoryn activity record as the main delivery record.

Use the connected Microsoft file path or export a supported document, then open it in New Fax with the intended account and destination.

If an authorization expires or a carrier is unavailable, the workspace should direct the person to reconnect or use another supported input path.

1. 01Authorize the intended Send a fax with Microsoft 365 account or workspace.
2. 02Select the minimum file, channel, or event permissions required.
3. 03Send one sample document through the connection.
4. 04Preview the file, send a sample, and confirm the final state in Faxoryn rather than treating an add-in action as delivery.

Remove the Send a fax with Microsoft 365 connection when it is no longer required, and revalidate it after ownership, credentials, or workspace policy changes.

Send a fax with Microsoft 365 may hold the original file, sent message, copied PDF, or notification, depending on the configured path. Faxoryn retains the fax record number, formatted destination, fax pages, carrier progress, and final delivered or failed state.

Record the source-system reference when the workflow must be matched later. A copied file or channel message can help a team find the work, but it must not be treated as independent proof that the fax destination received it.

• Confirm where the editable source and approved version are retained.
• Use the Faxoryn record number to investigate delivery and duplicate sending.
• Define whether connected copies are records, notifications, or temporary working files.

Authorization can expire, file permissions can change, an account can be removed, or Send a fax with Microsoft 365 can become temporarily unavailable. Surface that condition before sending whenever possible and do not silently omit a source file or event.

Reconnect only the intended account, then repeat the check with a sample document. For urgent work, use an approved local upload or workspace path and link the resulting record to the same business process without creating duplicate faxes.

A Send a fax with Microsoft 365 document can contain comments, tracked changes, hidden sheets, unsupported fonts, external links, animations, or access controls that do not survive fax preview. Select the approved version and inspect every fax page in Faxoryn.

Record which source file and version produced the fax when matching records later matters. A copied PDF in connected storage can support retention, but the Faxoryn activity record remains the record you can check for destination and carrier state.

• Confirm the intended account, tenant, file owner, and approved source version.
• Limit authorization scope and review shared-link or inherited access.
• Inspect fonts, page boundaries, hidden content, comments, and signatures after preview.
• Test revocation, expired authorization, missing files, and a local-upload fallback.

Document who owns the original, fax pages, sent copy, received copy, and final fax details. Set retention and deletion separately for connected storage and Faxoryn rather than assuming one system automatically governs the other.

When a user leaves or a connection changes ownership, revoke the authorization, check scheduled or event-driven copies, and try the replacement account with a sample document before restoring recurring work.