Skip to content

Commit 4b251d8

Browse files
authored
Update whats-deprecated-azure-ad.md
1 parent 00e5342 commit 4b251d8

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

articles/active-directory/fundamentals/whats-deprecated-azure-ad.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -47,14 +47,15 @@ Use the definitions in this section help clarify the state, availability, and su
4747

4848
|Category|Definition|Communication schedule|
4949
|---|---|---|
50-
|Deprecation|The state of a feature, functionality, or service no longer in active development. A deprecated feature may be retired and removed from future releases. Deprecated services might be retired in the future|?|
51-
|Retirement|Signals the retirement of a feature, capability, or product in a specified period. Customers can’t adopt the service or feature, and engineering investments are reduced. Later, the feature reaches end-of-life and is unavailable to any customer.|2 times per year: March and September|
52-
|Breaking change|The change might break the customer or partner experience if action isn’t taken, or a change made, for continued operation.|4 times per year: March, June, September, and December|
53-
|Feature change|Change to an IDNA feature that requires no customer action, but is noticeable to them. Typically, these changes are UI/UX.|4 times per year: March, June, September, and December|
50+
|Deprecation|The state of a feature, functionality, or service no longer in active development. A deprecated feature might be retired and removed from future releases.|?|
51+
|Retirement|Signals retirement in a specified period. Customers can’t adopt the service or feature, and engineering investments are reduced. Later, the feature reaches end-of-life and is unavailable to any customer.|2 times per year: March and September|
52+
|Breaking change|A change that might break the customer or partner experience if action isn’t taken, or a change made, for continued operation.|4 times per year: March, June, September, and December|
53+
|Feature change|Change to an IDNA feature that requires no customer action, but is noticeable to them. Typically, these changes are in the user interface/user experperience (UI/UX).|4 times per year: March, June, September, and December|
5454
|Rebranding|A new name, term, symbol, design, concept or combination thereof for an established brand to develop a differentiated experience.|As scheduled or announced|
5555

5656
#### Terminology
57-
57+
58+
* **End-of-life** -
5859
* **Tenant, current** -
5960
* **Tenant, new** -
6061

0 commit comments

Comments
 (0)