community
237 TopicsRequest on Exchange Server SE CU1 Codebase and Trial Version Behavior
Dear Microsoft Exchange Team and Community, I have questions about Exchange Server Subscription Edition (SE): Codebase of Exchange SE CU1 vs. Exchange 2019 CU15 The roadmap says Exchange SE RTM matches Exchange 2019 CU15 codebase, with new features starting in SE CU1. Is SE CU1 a standalone codebase or a direct continuation of Exchange 2019 CU15 with added features? Behavior after Exchange SE trial expiration What happens when the SE trial expires? Are all functions fully retained? Are any services or features restricted or disabled? Will the server remain usable? Thanks for your clarification!Solved283Views0likes4CommentsQuestion Regarding Exchange Server Usability Test/Development Environments
Hello dear community or Microsoft Teams, I recently posted a message in the general Exchange forum: Request on Exchange Server SE CU1 Codebase and Trial Version Behavior | Microsoft Community Hub I have already received some very helpful feedback – many thanks to the person who responded! However, one question remains unanswered: Is it legally questionable if the server continues to be used in a test environment after the trial version has expired? How is this handled? Now I have a specific question about ‘server usability’ after the trial version expires: ‘The server remains usable after the trial version expires, but is not legally licensed for productive use.’ How would this look in a test or development environment if the server is not used in a productive environment, but only for testing purposes? Are there any legal restrictions that need to be taken into account? I look forward to your answers and thank you in advance!42Views0likes0Comments'$skiptoken' limit error for Microsoft Exchange online Reporting web service API
I was working on integrating MessageTrace report API as a part of my SIEM integration: https://reports.office365.com/ecp/reportingwebservice/reporting.svc/MessageTrace[?ODATA%20options] I have noticed that, whenever my $skiptoken reaches the limit 999999 , it throws the following error with 500 status code: { "odata.error": { "code": "UnknownError", "message": { "lang": "", "value": "An error has occurred on the server." } } } It was working fine for the 999998 value, but wasn't for the $skiptoken value 999999. Is there any limitations on $skiptoken value from the API itself? Also, need information, if $skiptoken value 999999 exists, for example, "odata.nextLink": "../../reportingwebservice/reporting.svc/MessageTrace?$filter=StartDate%20eq%20DateTime'2024-12-02T00%3A00%3A00Z'%20and%20EndDate%20eq%20DateTime'2024-12-02T23%3A59%3A59Z'&$skiptoken=999999" then how can we request the data from next set of events? Can someone let me know, is there any max limit from Microsoft API side or for the $skiptoken?Solved141Views0likes2CommentsExchange Team blog got an upgrade!
We are excited to announce that Exchange Team blog got an upgrade! We wanted to enrich the experience of visiting our blog site, as well as wanted to improve the site design and add several features to the site. Firstly, you will notice that we are now hosted at the different URL, and our new home is at: http://msexchangeteam.com/ The new "main" RSS 2.0 feed link is: http://msexchangeteam.com/rss.aspx Then, you will notice that the whole site got a visual overhaul, hopefully it is more pleasing to view. Hope you like it! Few other things that are brand new: - The Videos section of the blog. Here we will be placing different videos that we will be recording occasionally - things like short interviews with members of Exchange product group, demos of something cool in Exchange and so on. Who knows, some Exchange party video might make it up there too! - The ability to add attachments to blog posts; no more posting of scripts in the body of the post (which can cause formatting and syntax issues later). All of the "old" links RSS links and feeds should keep on working (so the redirection is in place from old http://blogs.technet.com/exchange to new http://msexchangeteam.com/. We plan to keep this redirection in place for a good while, but just to make sure - you might want to update your RSS clients to point to the new URL so you can keep on getting your dose of Exchange-related goodness without any interruptions in the future! As always, feedback is welcome. Look out for more new features and improvements we are planning! - Exchange Team Blog crew1.4KViews0likes13Comments