Update point-in-time-restore-overview.md

[Amrinder-Singh29]

Added a clarification regarding version retention configuration for the PITR process.

[prmerger-automator[bot]]

@Amrinder-Singh29 : 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 3aeab5d:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
articles/storage/blobs/point-in-time-restore-overview.md	:white_check_mark:Succeeded

For more details, please refer to the build report.

For any questions, please:

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

[Court72]

@normesta

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

[normesta]

@Amrinder-Singh29 - Can we clarify exactly how choosing a retention period for versions will impact a point-in-time restore process? For example, if the customer sets a retention period of 5 days for versions, does this mean that a point-in-time restore operation cannot restore beyond that 5-day period because versions won't exist? I would be surprised with that because when those versions are deleted, they become soft-deleted versions. Those soft-deleted versions can be restored up to the soft-delete retention period. Because you cannot specify a point-in-time restore period that is greater than the soft-delete period, customers are protected against that unstable state. If we are going to add a note warning of the impact of version retention on point-in-time restore, we should be clear about what that impact is, and validate that behavior with the product team as this could be a potential bug that you are observing.

[normesta]

#please-close