Skip to content

Commit b5009c7

Browse files
Merge pull request #289631 from jaganth/docs-editor/message-expiration-1730419365
Update message-expiration.md
2 parents 052c57f + 47a70a7 commit b5009c7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/service-bus-messaging/message-expiration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ Service Bus queues, topics, and subscriptions can be created as temporary entiti
4949

5050
Automatic cleanup is useful in development and test scenarios in which entities are created dynamically and aren't cleaned up after use, due to some interruption of the test or debugging run. It's also useful when an application creates dynamic entities, such as a reply queue, for receiving responses back into a web server process, or into another relatively short-lived object where it's difficult to reliably clean up those entities when the object instance disappears.
5151

52-
The feature is enabled using the **auto delete on idle** property on the namespace. This property is set to the duration for which an entity must be idle (unused) before it's automatically deleted. The minimum value for this property is 5 minutes.
52+
The feature is enabled using the **auto delete on idle** property on the entity. This property is set to the duration for which an entity must be idle (unused) before it's automatically deleted. The minimum value for this property is 5 minutes.
5353

5454
> [!IMPORTANT]
5555
> Setting the Azure Resource Manager lock-level to [`CanNotDelete`](../azure-resource-manager/management/lock-resources.md), on the namespace or at a higher level doesn't prevent entities with `AutoDeleteOnIdle` from being deleted. If you don't want the entity to be deleted, set the `AutoDeleteOnIdle` property to `DataTime.MaxValue`.

0 commit comments

Comments
 (0)