search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.28k stars 21.46k forks source link

Update screenshots #45175

Closed SychevIgor closed 4 years ago

SychevIgor commented 4 years ago

Please, update screenshots - because in the end of 2019 - lists are significantly longer and we need to manually delete multipled extra items to finally deleted aad

https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/media/directory-delete-howto/delete-directory-list.png https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/media/directory-delete-howto/delete-checks-passed.png

image

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

shashishailaj commented 4 years ago

@SychevIgor Thank you for pointing this out . We are in the process of revamping the content and the screenshots and this is in the backlog. I am engaging the content authors to look into this.

Thank you.

shashishailaj commented 4 years ago

@curtand Could you please take a look on this one?

Thank you.

klawrawkz commented 4 years ago

imho, there needs to be an easier way to do this (decommissioning of azure+ms365). especially when we are working in with a dev subscription. in a lab environment, i need to create and destroy azure/365 tenants/directories/apps quickly. it seems like a waste of time to go through all this "decommissioning" of minutia in an environment that is created for experimentation only. clearly it would be a drag if i deleted a production directory accidentally. i can understand the rationale to make it slow and laborious in the "real" world. the reason i mention all this is that i note it is easy to spin up a new azure directory with all the bells and whistles in my dev subscription, but impossibly long and drawn out to delete them.

this leaves me to dwell and check in on services that i want to remove just to validate that they can be removed/are actually removed. i can be forgetful too, and that makes it harder for me b/c i can't remember if i need to go back and do more to get rid of some semi-defunct test environment. this seems like a total waste of time. let me say though, i am absolutely grateful to ms for the lab experience. is there a better way to spin up azure directories with dev ms365 apps and destroy the environment? what am i missing?

thanks,

klawrawkz

curtand commented 4 years ago

@SychevIgor
Thanks for reaching out. I have a work item open for this fix but don't have an ETA due to current priorities. We're also working on a much broader solution to out of date screens. I will not be updating the documentation immediately. If you determine another possible update to our documentation, please don’t hesitate to reach out again. #please-close

@klawrawkz .We recommend you reach out to the community at Microsoft Q&A to ask your question. If this is an issue with the product itself, then please contact Azure Support at [Azure support](insert link). If you determine another possible update to our documentation, please don’t hesitate to reach out again.