Update taken from D365 PR 6459

Author: phecke

powerapps-docs/developer/common-data-service/create-auto-number-attributes.md

@@ -32,7 +32,7 @@ The sequential segment is generated by SQL and hence uniqueness is guaranteed by
 > [!NOTE]
 >You can modify an existing format text attribute to be an auto-number format.
 
-When you add the auto-number attribute as a field to a form, the auto-number attribute field behaves as read-only in the form, and end-users cannot edit the field. The value is set only after you save the entity. You can see auto-number attribute as any other field value in views, grids and so on.
+In the legacy web client, when adding a control on a form bound to an auto-number attribute, the control is disabled automatically and behaves as read-only in the form where end-users cannot edit the control. In the Unified Interface, controls bound to an auto-number attribute need to explicitly be set as disabled. If you do not set the initial attribute value on the form, the value is set only after you save the entity. Auto-numbering can be applied to attribute field values in views, grids and so on.
 
 ### Examples
 The following examples show how to create a new auto-number attribute named **new\_SerialNumber** for a custom entity named **new\_Widget** which will have a value that looks like this: **WID-00001-AB7LSFG-20170913070240**.