![]() Today if you choose to download the report as a csv, the User agent data will be missing. The User agent field can be handy for identifying app versions, if the app sends the string that is, many apps don’t (and User agents can be modified).Īn easier way to view the data is to export it and use something like Excel to filter/group – as you likely will have a LOT of data. If you click on any of the lines, you’ll see more information in the pane below. Once you have your filter in place, you’ll see only those connections that meet the filter criteria (i.e. If you have custom apps you’ll see them here, the screenshot below shows only the defaults provided. When non-browser clients are using Modern Auth they will be placed into the Mobile Apps and Desktop Clients group. To view Basic Auth connections today you should select everything except Browser and Mobile Apps and Desktop Clients. Now you can add a filter, Client app (then apply), and then a new dialog will allow you to pick the client app(s) to view. You can add columns, and we’d suggest you add Client app if it’s not already there. On this overview page you’ll see the sign-in activity in your tenant, dates, times, user IP address and so on. ![]() It’s typically available in the side menu under Azure Active Directory, and you can always search if you can’t find it. The report is part of the Azure Active Directory admin center, called Sign-ins. Take a look at a blog the Identity team posted that will help you use some of the more advanced features available within the report. The report has recently been extended to include data you’ll find helpful for identifying clients and apps still using Basic Auth, and we have more updates coming soon. We still have work to do on it, but we decided we’d rather get the word out now as we continue to work on it than wait until it’s all complete. The first piece of news is that the improved Azure Sign-In report which can help you understand Basic Auth usage in your tenant is available. We do understand a change like this can be disruptive. We’re pleased to provide an update today and to try and answer some of the questions we’ve received since that post. It’s been a few months since we announced changes we will be making to Exchange Online to improve security. ![]() Update: The full timeline for retirement of Basic Authentication in Exchange Online is now published in Basic Authentication Deprecation in Exchange Online – September 2022 Update.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |