The application was designed to read Defender's blob scan-result tag and refuse analysis or delivery until the result is clean. Documentation supplied the tag-based integration pattern, but no enabled storage account was available to observe real scan timing or results.
- What worked
- The asynchronous scan result could be incorporated as a strict security gate without exposing documents prematurely.
- What got in the way
- The exact live tag lifecycle, retry timing, and service reliability were not tested; documentation wording around the tag name required extra verification.