Microsoft Graph is evolving. It\u2019s starting to expand beyond the well-known boundaries of its transactional datasets. This evolution is on full display at Ignite 2020.\u00a0 You\u2019ll see that our engineers are working hard to further extend its capabilities \u2013 and even its definition \u2013 to expose Microsoft 365 infrastructure, capabilities and tools that can help developers build new classes of high-value, trusted applications.\u00a0 To start this blog, we\u2019ll share four examples of newly announced services that you can use \u2013 today, and of course we\u2019ll also share updates on all the other Microsoft Graph news & announcements too!<\/p>\n
1.\u00a0\u00a0\u00a0\u00a0 Microsoft Graph Connectors<\/strong><\/p>\n In just about any organization you\u2019ll find important information stored in discrete silos. These silos are significant barriers to productivity, where even the task of locating needed information is complex if not impossible. So, we\u2019re very excited to announce that Microsoft Graph Connectors<\/strong><\/a> are now generally available<\/strong>. By building your own connector or buying one of the dozens of connectors already available<\/a> you can bring data from just about any source – Service Now, MediaWiki, even documents stored in other clouds or services like Box – into Microsoft Graph to take advantage of the enterprise search capabilities of your Microsoft 365 tenant.\u00a0 We\u2019ve got all you need to get started building a connector of your own your own.<\/p>\n 2.\u00a0\u00a0\u00a0\u00a0 Azure Communication Services (ACS)<\/strong><\/p>\n Today, connectors offer developers and customers access to enterprise search \u2013 a powerful Microsoft 365 product feature. But we\u2019re also making it possible to access services powered by Microsoft 365\u2019s enterprise-scale infrastructure.\u00a0 Today we\u2019re announcing the public preview of <\/strong>Azure Communication Services<\/strong><\/a> (ACS).<\/strong> ACS\u00a0is a set of\u00a0rich\u00a0communications APIs\u00a0that you use to integrate secure, encrypted communications services into any application \u2013 on any platform. ACS is built on the same enterprise-grade infrastructure that powers the voice, video and messaging services for Microsoft Teams. But what\u2019s new \u2013 and important \u2013 is that unlike any previous Microsoft 365 Graph-powered experience, ACS is offered as a Azure service. This means that the billing and management for your app\u2019s use of these communications services is based on consumption rather than user licensing, and it\u2019s consolidated with the rest of your app\u2019s Azure infrastructure.\u00a0 Start learning more about the new ACS APIs today.<\/p>\n 3.\u00a0\u00a0\u00a0\u00a0 Security and Compliance Services<\/strong><\/p>\n At Build 2020 we offered a preview of a new Teams Chat webhook API<\/strong><\/a> , one of a number of Microsoft Graph APIs that extend our 1st<\/sup> party Security and Compliance services to our ecosystem.\u00a0 This week at Ignite we\u2019re significantly expanding our preview to include an Advanced eDiscovery API<\/strong> and a Teams Export API<\/strong>. With this expanded preview, developers can start to explore the power of extending and tailoring these services to meet the specific DLP and compliance needs of their internal or external customers and partners.<\/p>\n 4.\u00a0\u00a0\u00a0\u00a0 Universal Print<\/strong><\/p>\n Even in an increasingly digital word, simple, cost-effective printing is still a necessity for any organization. Universal Print<\/strong> is a new enterprise cloud print service that allows users to print to any printer managed by their organization from any device using their Azure Active Directory (Azure AD) credentials. We\u2019re previewing a new API for this service \u2013 one that helps you to manage the settings & capabilities<\/a> of printers, and we\u2019ve expanded permission scopes<\/a> to define app & delegated permissions for this service. We\u2019ll continue to expand our preview of Universal Print in the coming months.<\/p>\n Microsoft Teams APIs<\/strong><\/p>\n Making sure the right people have managed access to the right teams, channels and content is critical. We have a new preview version (R4) of Resource Specific Consent<\/strong>, now available to all developers. Its usage remains limited to calling data APIs, but we expect to lift that restriction and move it into production in a matter of a months. We\u2019re also pleased\u00a0to announce general availability of<\/strong> Team\u00a0Membership\u00a0APIs<\/strong><\/a>.\u00a0 These APIs allow\u00a0your app\u00a0to\u00a0list, add, change, and remove Team members and their roles. We\u2019re also moving new resource types that allow apps to create and manage private channels<\/strong><\/a> within a group generally available. Of course, we also want to make sure that appropriate message content remains secure within the boundaries of an organization, and are announcing the upcoming general availability of our <\/strong>Teams Chat Webhook API<\/strong><\/a> (previously mentioned), designed for use in DLP scenarios.<\/p>\n We\u2019ve consistently heard from developers who want more ways for their apps to engage users within their flow of work \u2013 for example within the activity feed, or adjacent to an online meeting.\u00a0 We\u2019re responding by offering a preview of the new Microsoft Graph API for Activity feed notifications<\/a>. And\u00a0 Microsoft Teams meeting extensibility takes this a step further, with the announcement that meetings extensibility APIs<\/strong><\/a> are now generally available<\/strong>.<\/p>\n To-Do tasks API<\/strong><\/p>\n Task lists are a core productivity function and we\u2019re giving them a new look with the preview Microsoft To Do API<\/a>. \u00a0This new API allows app users to organize and track personal tasks across Microsoft 365 client apps and replaces the older Outlook Tasks API.<\/p>\n Search API<\/strong><\/p>\n We\u2019ve made updates to the Microsoft Graph Search API<\/strong><\/a>, which is currently in beta, to bring an even richer, more unified API endpoint for search content in Microsoft 365.\u00a0 It is now possible to search and filter across more types: listitems, lists, sites and drives in SharePoint and OneDrive, and developers can sort and refine search results, as well.\u00a0 We\u2019ve also made it possible to Search across multiple Microsoft Graph Connectors. We are expecting to make the Microsoft Graph Search API generally available by the end of 2020, so keep an eye out for announcements.<\/p>\n Taxonomy API<\/strong><\/p>\n At Build 2020 we gave a teaser of Project Cortex, which uses AI tools to help you find, identify, classify, and present data that is rich with content and context from your organization, and also the associated Taxonomy API, which lets you create and manage your own term stores for use with this technology.\u00a0 You can now find detailed information on using the preview Taxonomy APIs<\/a> in our beta reference.<\/p>\n Identity API announcements<\/strong><\/p>\n Many of our Microsoft 365 customers use Azure AD Conditional Access as their Zero Trust policy engine. So we\u2019re pleased that today we are announcing the general availability of the Azure AD Conditional Access API<\/strong><\/a>. Azure AD Conditional Access helps ensure that the right people have\u00a0the access\u00a0to resources they need from wherever they are. We\u2019re also announcing general availability of <\/strong>advanced queries in Microsoft Graph for directory objects<\/strong><\/a>. With advanced queries, you can easily search, sort, count and order directory objects like users, devices, and applications.<\/p>\n Microsoft Graph Toolkit 2.0<\/strong><\/p>\n Graph Toolkit is one of our go-to developer assets. That\u2019s why we\u2019re excited to announce the upcoming 2.0 release of the Microsoft Graph Toolkit<\/a>. In this update we\u2019ve added all sorts of new and improved features, from improved \u201cGetting Started\u201d guides to new and updated MGT\u00a0packages, components and features that are easy to use, versatile and will significantly accelerate development of your app\u2019s Microsoft Graph-powered integrations.<\/p>\n PowerShell SDK<\/strong><\/p>\n Last year at Ignite we introduced the PowerShell SDK to great fanfare, with a huge crowd, at a theatre overflowing with developers and IT administrators. We don\u2019t have the live audience this year, but are still very pleased to announce that the Microsoft Graph PowerShell SDK<\/strong><\/a> is generally available<\/strong> \u2013 and with it, straightforward, consistent access to insights and capabilities spanning the entire surface of Microsoft Graph.<\/p>\n Customers \u2013 and specifically, IT administrators, must trust any app they\u2019d even consider installing in a Microsoft 365 tenant. To fortify that trust, we now offer the Microsoft 365 App Compliance program<\/strong>.<\/a> There are three components to this program \u2013 Attestation, Verification and Certification.\u00a0 And it makes a difference, as we\u2019re already hearing from partners:<\/p>\n \u201cIt\u2019s been just a few weeks and we are already experiencing benefits in security screening.\u00a0 Being Microsoft 365 certified is an enormous time-saver for both us and our customers.\u00a0 It is a critical offering and it helps us stand out in the market.\u201d<\/em>\u00a0 Martin Siefert, CEO at Officeatwork<\/strong><\/p>\n App certification<\/strong><\/p>\n Publishers can work with Microsoft to certify that their app \u2013 and its supporting infrastructure \u2013 protect the security and privacy of sensitive customer data.\u00a0 Certified apps receive a badge that is visible in AppSource and from within the Microsoft 365 tenant administrator\u2019s console.<\/p>\n Today, our certification program supports Microsoft Teams Add-ins. Over time, we will extend the program to include Office Add-ins, and SharePoint Framework (SPFX). We strongly encourage app publishers to take advantage of this program, and over time, expect to make it a requirement.<\/p>\n Publisher verification<\/strong><\/p>\n We announced the public preview of Publisher Verification at Build 2020, and since then have verified over 600 publishers. Today, we\u2019re announcing that Publisher Verification is now generally available<\/strong><\/a>. <\/strong>Now, app publishers can demonstrate to customers that their application comes from a Microsoft-verified source.<\/p>\n With general availability, Microsoft will make changes to our app consent policies and block end-users\u2019 ability to consent to newly created multi-tenant apps having an unverified publisher. The consent screen will clearly indicate that these apps are risky and unverified. Note that this change will not affect apps requesting basic sign-in and permissions to read user profile.\u00a0 Nor will it affect apps requesting consent in their own tenants. We\u2019ll be sharing more about these changes soon. To prepare for this change, add a verified publisher to all your multi-tenant apps.<\/p>\n We hope this blog offered you a good overview of the full range of initiatives we\u2019ve undertaken to expand and enrich the capabilities of Microsoft Graph.\u00a0 We\u2019d love to see how you use it to build richer, more connected, more beautifully integrated applications that customers trust and value \u2013 and of coure deploy and use to transform the future of their own workplaces.\u00a0 Be sure to visit the Virtual Hub<\/a> for all the skilling content we\u2019ve created, and of course you\u2019re always welcome to join our Microsoft 365 developer community<\/a>.<\/p>\n <\/p>\n Thanks for attending Ignite 2020 and happy coding.<\/p>\n The Microsoft Graph Team<\/p>\n <\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Learn how our engineers are working hard to extend the capabilities and even the definition of Microsoft Graph for developers building the next generation of productivity applications.<\/p>\n","protected":false},"author":69076,"featured_media":25159,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3],"tags":[114],"class_list":["post-5348","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-graph","tag-microsoft-ignite"],"acf":[],"blog_post_summary":" Learn how our engineers are working hard to extend the capabilities and even the definition of Microsoft Graph for developers building the next generation of productivity applications.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/5348","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/users\/69076"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=5348"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/5348\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/25159"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=5348"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=5348"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=5348"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}New Tools & APIs<\/h3>\n
Microsoft 365 app compliance program<\/h3>\n
In Closing\u2026<\/h3>\n