ATOM API update, should use distinct class from create for non-writeable fields #12414
Labels
blocking-release
Blocks release
Client
This issue points to a problem in the data-plane of the library.
Service Bus
Milestone
Should we limit the fields that we allow to be updateable when performing an Update operation vs Create?
(to better communicate to a user that certain fields cannot be changed and will error)
The text was updated successfully, but these errors were encountered: