Update: Deprecation of Client Access Rules in Exchange Online

Update: Deprecation of Client Access Rules in Exchange Online

This article is contributed. See the original author and article here.

Last September, we announced the deprecation of Client Access Rules (CARs) in Exchange Online. CARs allow admins to control which devices can access their organization’s mailboxes. It was introduced in 2017 as a way to provide granular access control based on client properties such as IP addresses, protocol, or application.


In October 2022, we disabled CARs cmdlets for tenants that were not using CARs. This was done to reduce the complexity and confusion around CARs and to encourage the adoption of newer and more secure features like Azure Active Directory (AAD) Conditional Access and Continuous access evaluation (CAE).


We have been working with customers to learn how they use CARs and how they can migrate to these newer features, but we have encountered a few scenarios where it’s not possible to migrate current rules. For these scenarios, we will allow the use of CARs beyond the previously announced September 2023 deadline until we can support them.


We understand that migrating from CARs to Conditional Access and CAE requires some planning and testing, and we are here to help you with this process. If there is a technical reason preventing you from migrating your CARs, please open a support ticket so we can investigate and understand your needs.


Our updated CARs deprecation timeline is as follows:


CARsUpdate01.jpg


Resources



The Exchange Team

Join us at the AIIM Conference 2023, April 25-27

Join us at the AIIM Conference 2023, April 25-27

This article is contributed. See the original author and article here.

Connect with the Microsoft team on April 25-27 for the AIIM Conference 2023 (AIIM23) in New Orleans at the Hyatt Regency to learn more about business drivers and current trends impacting information management.  


AIIM23.png


As an Elite Diamond Sponsor of this year’s conference, we’re excited to connect with the AIIM community of information management professionals! AIIM23 is three days of collaborative learning designed to help you master your organization’s content to operate more effectively, reduce costs, and manage risk. You’ll learn about transforming how business content is captured/created, processed/shared, and discovered/protected – so you can empower your people, enhance the customer experience, and drive business value. 


 


We’ll have a large presence at AIIM23 representing Microsoft Syntex, Viva, and Purview. We’re looking forward to engaging with you during the event: 



  • Attend our keynote and sessions to learn more about our Future of Work vision (all times in CDT) 

    • Keynote: Unlocking productivity with Microsoft and Next-Generation AI with Marco Casalaina (VP, Products, Azure Cognitive Services) | April 26, 1:35-2:05pm 

    • Session: Introducing Microsoft Syntex – Content AI for the Microsoft Cloud with Kristen Kamath (Principal Product Manager, Microsoft Syntex) | April 26, 12:05-1:35pm 

    • Session: Microsoft Viva Topics – Empower your workforce with next-generation AI with Chris McNulty (Director, Product Marketing, Microsoft 365) | April 26, 3:55-4:25pm 

    • Session: How the World’s Largest Companies Deploy Microsoft Purview Records Management with Brendon Lee (Senior Product Manager, Microsoft Data Lifecycle and Records Management) | TBD 

    • Keynote panel: Information Management in the Age of AI with Marco Casalaina | April 27, 9:00-9:45am 



  • Visit our booth to talk to our team and our partners, attend mini-sessions, view new demos, ask questions, and get Syntex and Viva swag 

  • Go to the AIIM23 attendee party – sponsored by Microsoft 


If you’re a customer attending AIIM23 or in the New Orleans area, you can also request a 1:1 meeting with our product team members and Global Black Belts.  


 


Register for AIIM23 today! Use the discount code MICROSOFT_GUEST to save $100 on registration. 


 


More upcoming events 


In addition to AIIM23, we’d love to see you at one of the events below: 


 


AIIM Webinar on Content AI and Microsoft Syntex  


Is Content AI really a game-changer in business today? Find out at our upcoming webinar with AIIM on April 19, 11:00am PDT! Register for this webinar today and you’ll hear what Content AI is and learn some important best practices to leverage AI so you can enhance your content’s value and manage it at scale.  


 


Microsoft 365 Conference 


Catch up with us at the Microsoft 365 Conference, May 2-4, at the MGM Grand in Las Vegas. You’ll meet others in the Microsoft community from around the world as you learn about the latest collaboration tools and AI capabilities that are transforming the workplace and can help you grow your impact and career. Read the Microsoft 365 Conference blogpost to learn more about the event. Use discount code MSCUST150 to get $150 off conference registration. 


 


Document Strategy Forum (DSF) ’23 


Join us at DSF ’23 Charlotte, May 22-24 at Le Méridien Charlotte to learn more about how to create and manage content, communications, and strategies to support customer experiences. As a Corporate sponsor this year, you’ll find us at our keynote and at booth #303 talking about our Content AI solutions, including Microsoft Syntex. Read our Springtime is Syntex time blogpost to see how you can meet and engage with us. Use discount code DSF23VIP to save up to $600 on conference registration or receive a free exhibit hall pass. 


 


We’re looking forward to seeing you in New Orleans or at an upcoming in-person or virtual event! 

Pipeline Logic 3: Error Handling and Try Catch

Pipeline Logic 3: Error Handling and Try Catch

This article is contributed. See the original author and article here.

Series Overview


Orchestration allows conditional logic and enables users to take different paths based upon outcomes of a previous activity. Building upon the concepts of conditional paths, ADF and Synapse Pipelines allow users to build versatile and resilient workflows that can handle unexpected errors that work smoothly in auto-pilot mode.


 


This is an ongoing series that gradually levels up and helps you build even more complicated logic to handle more scenarios. We will walk through examples for some common use cases, and help you to build functional and useful workflows.


 


Please review the first installment in the series: Part 1: Error Handling and Best Effort Step and Part 2: OR


 


Error Handling and Try Catch


Error handling is a very common scenario in data engineering pipelines. From time to time, activities will fail, but we don’t want to fail the whole pipeline due to a single activity failure. 


 


We call this logic: Try-Catch, and we have streamlined the implementation for this common use case.


 


conditional-complex-2.png


 



  • Add first activity



  • Add error handling to the UponFailure path



  • Add second activity, but don’t connect to the first activity



  • Connect both UponFailure and UponSkip paths from the error handling activity to the second activity.

     




To learn more, read Pipeline failure and error message – Azure Data Factory | Microsoft Learn


 


We hope that you have found this blog to be helpful! If you have any questions or feedback, please post them in the comments below. 


 

Public preview: Programmatically interact with Microsoft Purview workflows using APIs and SDKs

This article is contributed. See the original author and article here.

To increase our developer experience landscape and to allow customers to interact and extend Microsoft Purview functionality using software technologies and tools in their organization, we are happy to announce that REST APIs and SDKs for workflow data plane in public preview. Software engineers or developers in your organization can now leverage these APIs/SDKs to programmatically create or update a workflow, submit a workflow, approve or reject an action, update or re-assign an approval or task action, list or cancel workflow runs, and more.


 


In order to use any Microsoft Purview data plane APIs you need to first create a service principal and assign it to the right Microsoft Purview role before invoking the APIs. This is needed to establish trust between the service principal and the Microsoft Purview account. For example, to create a new self-service data access request workflow and bind the same to root collection, you need to provide ‘Workflow Admin’ role to the service principal at the root collection level. 


 


This tutorial covers details on how to create service principal, set up authentication using the service principal, get token and use the token to call Microsoft Purview data plane APIs.


 


To get started with workflow data plane APIs and SDK’s please see the below links:



  • Workflow data plane APIs, see here.

  • Workflow data plane C# SDK, see here.

  • Workflow data plane Java SDK, see here.

  • Workflow data plane Python SDK, see here.

  • Workflow data plane Java script SDK, see here.