added new scenario for Front Door

[kostinams]

added new page about reliable content upload using Front Door and Azure Blob Storage

[prmerger-automator[bot]]

@kostinams : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod[bot]]

Learn Build status updates of commit 4d53980:

:warning: Validation status: warnings

File	Status	Preview URL	Details
articles/frontdoor/scenario-upload-storage-blobs.md	:warning:Warning		Details
articles/frontdoor/media/scenarios/origin.png	:white_check_mark:Succeeded
articles/frontdoor/media/scenarios/route-configuration.png	:white_check_mark:Succeeded
articles/frontdoor/media/scenarios/ruleset.png	:white_check_mark:Succeeded
articles/frontdoor/media/scenarios/upload-blob-front-door-architecture.png	:white_check_mark:Succeeded
articles/frontdoor/media/scenarios/upload-blob-front-door-architecture-highres.png	:white_check_mark:Succeeded
articles/frontdoor/TOC.yml	:white_check_mark:Succeeded

articles/frontdoor/scenario-upload-storage-blobs.md

• Line 5, Column 9: [Warning: author-not-found - See documentation] Invalid value for author: 'irkostin' is not a valid GitHub ID.
• Line 49, Column 1: [Warning: sensitive-language-wl - See documentation] Term 'whitelist' is sensitive and should not be used in content or code. Usage: 'By using Azure Front Door in front of the Azure Storage accounts it allows customers only whitelist one single domain for content upload. '
• Line 63, Column 1: [Warning: file-not-found - See documentation] Invalid file link: 'origin.png'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Court72]

Hi @kostinams,

Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.

After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.

Read about authors working in the public repo for more information.

If you need help getting set up to work in the private repo, see Get started contributing to the Microsoft Learn platform.

We'll close this PR. Thank you.