Adjust length of Workflow ID to prevent credit card misidentification by M365

Stephen Haskin

We have recently implemented some automated workflows, and have found that Microsoft 365 identifies automated emails from Smartsheet as credit cards. If we try to forward those emails to external users, or if an external user replies to that email and starts a thread with us, Microsoft 365 flags the email every time because the Workflow ID is being interpreted as a credit card number. In our enterprise, this requires us to delete the offending info or make several additional clicks for an override (which the average end user could have trouble with).

I discovered that deleting the Workflow ID removes the warning, so I am assuming the workflow ID is the same length as a credit card number.

Suggestion: Can workflow ID digit length be adjusted to reduce/eliminate the risk of false identification as a credit card number?

druththetech

We are seeing the same issue, and any other organization that is using an email filtering rule to identify and block email messages that contain credit card numbers will have the same problem. Smartsheet could change the length of the workflow ID as suggested in this post, make it alphanumeric, or at least change the numbering of IDs so that they don't start with known credit card BINs.