This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
I'm wondering how I must interpret the three filters we have in this page:
Do these status have a sequence connection among them?
For instance In development will become In Preview and then Now available... Yes? No?
Some "Now Available" items report the Target Availability; other not; why?
As soon as an item classified as "In Development" will be released, will it disappear from this category to appear under in Preview or Now Available? Yes? No?
Thanks a lot in advance,
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 63%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETM%3C/text%3E%3C/svg%3E)
Hi,
I can't answer this question with authority however I will give my understand and someone can tell me if I am right or wrong.
Items move up from in dev -> preview -> available. However items can start at any stage so you could have a feature go straight to available. I would expect that items can not move back stages however as taking something from available to preview would have a large impact on trust and ToS.
Target Availability - I suspect these are left over from in-preview items that are 'moved' to available.
Anything in preview is exactly that in preview and it can be removed or deprecated at any point. Not sure we have seen this in practice all that much but the ToS for in preview items states that it should not be used for production use cases due to changes and the potential features could be removed.
Hope that helps.
Thanks @Thomas Mead
I have some doubts about what is the process behind it because, for instance, some items in Now Available status report wrong statement about the target availability OR the "In Development" status still report very obsolete items (2021) instead of being removed.
I think the idea is that this is not a curated list of features for any product as we have docs for that. Instead this is a means for the Azure teams to communicate what is being worked on and what is coming up at a point in time. Hence the removal of In Development items is likely not the right idea as this should be a history of updates. If that development item never moves on thats fine but the update was right for the time period. Granted I would expect an update later that states the removal or not doing status of that project.
The target availability is odd and I suspect this is an admin error or intentional and is there to state when something was planed for release. Not sure the value of the latter however.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Normally a feature will progress from in development to preview to supported (available). But a feature in development or preview can be dropped, and not progress any farther.