Merge pull request #189146 from spelluru/patch-84

CanNotDelete doesn't affect AutoDeleteOnIdle

Author: PRMerger14

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

@@ -44,6 +44,9 @@ Service Bus queues, topics, and subscriptions can be created as temporary entiti
 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.
 
 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.
+
+> [!IMPORTANT]
+> Setting the 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` configured from being deleted. If you don't want the entity to be deleted, set the `AutoDeleteOnIdle` property to `DataTime.MaxValue`. 
  
 ## Idleness
 
@@ -83,4 +86,4 @@ To learn more about Service Bus messaging, see the following articles:
 - [Geo-disaster recovery](service-bus-geo-dr.md)
 - [Asynchronous messaging patterns and high availability](service-bus-async-messaging.md)
 - [Handling outages and disasters](service-bus-outages-disasters.md)
-- [Throttling](service-bus-throttling.md)
+- [Throttling](service-bus-throttling.md)