<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mittal Saurabh on Medium]]></title>
        <description><![CDATA[Stories by Mittal Saurabh on Medium]]></description>
        <link>https://medium.com/@mittal.saurabh89?source=rss-63c014d33590------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*eTnxW269iUqj89cFZt3d1g@2x.jpeg</url>
            <title>Stories by Mittal Saurabh on Medium</title>
            <link>https://medium.com/@mittal.saurabh89?source=rss-63c014d33590------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 18:51:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mittal.saurabh89/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Secure & Flexible Employee Access with Google Workspace]]></title>
            <link>https://medium.com/@mittal.saurabh89/secure-flexible-employee-access-with-google-workspace-9c7857420977?source=rss-63c014d33590------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c7857420977</guid>
            <dc:creator><![CDATA[Mittal Saurabh]]></dc:creator>
            <pubDate>Tue, 01 Nov 2022 11:39:14 GMT</pubDate>
            <atom:updated>2022-11-01T12:00:14.507Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Secure &amp; Flexible Employee Access with Google Workspace</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*_ZPdiIxutVzl1bzEdOEFPg.png" /></figure><p>Organisations need secure employee access to business applications from wherever the employee is working.</p><p>The workplace is transforming from an on-premise office environment to a distributed workforce that can work from anywhere .With these changes business need to secure and control access to business applications and data from where-ever the employee may be. The use of VPN solutions can create daily friction for the employees and reduce productivity while adding management overhead for the IT Teams.</p><p>Providing secure employee access while maintaining simplicity and flexibility is important part of business productivity and success , now more than ever in this new normal.</p><p><strong>Solution : </strong>Google Workspace Context Aware Access</p><p>Context Aware access provides granular level application access controls based on attributes of employee device, location and network. If the specified attributes are matched the employee is automatically denied or granted access. This provides the organisation secure access control policies for their employees where-ever they are working from, without the overhead of VPN.</p><p><strong>What is Context Aware Access ?</strong></p><p>Context-Aware Access gives you control over which apps a user can access based on their context, such as whether their device complies with your IT policy. Using Context-Aware Access, you can create granular access control policies for apps that give access to Google workspace data based on attributes, such as user identity, location, device security status, and IP address or combination of multiple attributes. The administrator can customise this policy for a specific member’s of OU or using a google group ensuring that each user is meeting the specific requirement they have.</p><p><strong>SKU : Licensing Options</strong></p><p>Supported Google Workspace editions for context aware access are Business SKU , Enterprise Essential , Enterprise Standard , Enterprise Plus, Education Standard and Education Plus ; Cloud Identity Premium</p><p>Users who don’t have one of the supported editions aren’t subject to Context-Aware Access policies that are enforced in their organisational unit or group.</p><p><strong>Applications Supported by Context Aware Access</strong></p><p>You can apply Context-Aware Access policies to Google workspaces web apps on desktop, mobile apps, and native apps on desktop. Access for apps is evaluated continuously after access is granted. The exception is SAML apps, which are evaluated on sign-in.</p><p><strong>Difference between Google Context Aware Access and Azure AD Conditional Access</strong></p><p>Both Google and Microsoft Azure provide conditional access services to improve security posture and how can securely access business applications which are provided natively by them and other SAML business applications.</p><p>One of the Key difference b/w Google( context aware access )and Azure’s ( conditional access policies) is that while Google’s context aware access can only block or grant access, Azure AD conditional access provides an option where user can be granted limited access to the app if certain conditions are met , such as it becomes necessary for the user to have multi-factor authentication to get limited access to app or be granted read only access to app if accessing from a non-compliant devices.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c7857420977" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interoperability between Google Meet, Meet Hardware Kits and 3rd Party Video Conferencing Systems]]></title>
            <link>https://medium.com/@mittal.saurabh89/interoperability-between-google-meet-meet-hardware-kits-and-3rd-party-video-conferencing-systems-2f05fc466385?source=rss-63c014d33590------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f05fc466385</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[google-workspace]]></category>
            <category><![CDATA[google-meet]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Mittal Saurabh]]></dc:creator>
            <pubDate>Fri, 16 Sep 2022 14:45:14 GMT</pubDate>
            <atom:updated>2022-09-16T14:45:14.664Z</atom:updated>
            <content:encoded><![CDATA[<p>Interoperability between Google Meet, Meet Hardware Kits and 3rd Party Video Conferencing Systems</p><p>Google Workspace offers Google meet as the secure , high quality native video conferencing platform which allows users to connect with people in this era of any device , anywhere , anytime . Google also offers fast, effective, easy video meetings solutions for all your rooms and spaces with Google Meet hardware kits based on Chrome OS allows organisations to extend their Google Meet Collaboration Platform to small meeting rooms spaces and large conference rooms .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/551/1*0ZLVCpG8Mv4KOYSaSUMQeA.png" /><figcaption>Google Meet Hardware Kit Powered with ChromeOS</figcaption></figure><p>As the Google workspace adoption is increasing especially in the enterprise segment and Customers also using standard based room-video conferencing solutions like MS Teams, Cisco Webex, Polycom, Sony etc it becomes important for these enterprise to have interoperability in place between Google Meet and other video conferencing solution to cater to different business needs.</p><p>Some of the major use cases due to which need for interoperability can arise are as below :</p><ol><li>Your organisation is migrating to Google Workspace and will be adopting Google Meet and Google Meet Hardware Kit ( room VC solutions ) as default VC solution. In such case you may have exiting VC solutions like Cisco , Polycom etc which you will be slowly replacing with Google Meet or Google Meet Hardware kits , in such situation till the time migration is not completed certain co-existence is required between both the solutions so that users/rooms who have been migrated to Google meet can join meetings on other platforms as well and work together with people using other VC solutions.</li><li>External Collaboration : If you are already using Google Meet as your VC platform but your users need to frequently collaborate with external stakeholders , partners or group companies users who are not using Google Meet as their video conferencing solution , then setting up a co-existence between Google meet and 3rd party video conferencing systems can be very useful.</li><li>Have mixed communication environment , where you need to connect with Google Meet from other systems and vice versa.</li></ol><p>So let us what options we have for setting up interoperability between Google Meet and 3rd party VC systems</p><p><strong>Native functionality </strong>: Google has introduced video conferencing interoperability for Google Meet with Cisco Webex, which will allow you to:</p><ul><li>Join Webex meetings from Google Meet hardware devices</li><li>Join Google Meet calls from supported Cisco Webex devices</li></ul><p>Key Points to note regarding native interoperability are :</p><ul><li>This interoperability will support only core video conferencing features .</li><li>Some advanced features, such as polls, breakout rooms, and dual-screen support, present via HDMI may not be available when using Meet hardware to join Webex calls and vice versa.</li><li>Interoperability feature will be turned on by default, Meet Hardware devices will be able to dial into Webex meetings by default — Admins can disable this feature for specific organisational units via the Google Meet Hardware Settings page in the Admin console.</li><li>By default, participants joining using a Cisco Webex device must be admitted to the Meet meeting by someone already in the meeting. As an administrator, you can allow Cisco Webex devices to join Meet meeting without asking by generating an interop token ( from google admin console )and adding it to the Cisco Webex Control Hub ( in Cisco Webex admin console)</li><li>You cannot join Webex meetings from meet for web or mobile.</li><li>Webex Host can record the meeting.</li></ul><p><strong>Third Party Solutions</strong> : For interoperability needs outside of Cisco Webex, Google recommends Pexip. Pexip enables joining Meet calls from the widest range of third-party video conferencing hardware.</p><p>The Pexip Google Meet interoperability solution connects third-party video conferencing devices and systems to natively join Meet calls. It extends the use of Meet across organisations that have multiple video meeting solutions from vendors such as Cisco and Polycom, or even Skype for Business.</p><p>Key Features for offered by Pexip Connector/Infinity Gateway ( this is the connector which will act as bridge for Google Meet and 3rd party VC) are :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/0*Fd58sASKkWXlFugD" /><figcaption>Pexip Reference Architecture</figcaption></figure><ol><li>Pexip for Google Meet enables non-Google users to join Meet video calls using a SIP or H.323 video conferencing system, Skype for Business, or non-Google web browsers.</li><li>Works with Google Calendar : You can continue setting up meetings the way you used to with no additional software required.</li><li>The Pexip Infinity gateway can be deployed as a service running on Google Cloud (Pexip hosts, operates, and supports the service and its functionality so you don’t have to), on a company’s own Google Cloud instance, on-premise, or both (hybrid mode). Number of license you need for Pexip will depend number of concurrent systems that are connecting to the Google Meet.</li><li>Also supports Google Meet hardware kits and Jam-boards to join H.323 or SIP based video conferencing device meetings.</li><li>Pexip is easy to configure in Google Workspace. Simply apply the correct license and go through a few simple configuration steps, then start meeting.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/553/1*2bDCSqdFLsw-ny1NMcV2Xg.png" /><figcaption>Pexip Connector for Google Meet</figcaption></figure><p>So this blog post summarises the different options available to setup Google Meet and 3rd party systems interoperability to suite your various needs. These solutions can be especially useful in case of short term co-existence during migrations to Google workspace or when you are migrating from legacy video conferencing solutions to Google Meet Hardware kits.</p><p>Hope this blog post is useful in giving you a overview on how Google Meet can co-exist with other solutions and offer interoperability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f05fc466385" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[{Part3 }Identity Co-existence : Using Azure AD as Identity provider for Google Workspace]]></title>
            <link>https://medium.com/@mittal.saurabh89/part3-identity-co-existence-using-azure-ad-as-identity-provider-for-google-workspace-d2c8508c39ed?source=rss-63c014d33590------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2c8508c39ed</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[g-suite]]></category>
            <category><![CDATA[office-365]]></category>
            <category><![CDATA[azure-active-directory]]></category>
            <category><![CDATA[google-cloud-identity]]></category>
            <dc:creator><![CDATA[Mittal Saurabh]]></dc:creator>
            <pubDate>Sun, 29 May 2022 11:12:53 GMT</pubDate>
            <atom:updated>2022-05-29T11:25:59.456Z</atom:updated>
            <content:encoded><![CDATA[<h3>{Part3 }Identity Co-existence : Using Azure AD as Identity provider for Google Workspace</h3><p>If you have been following my previous blogs we talked about how you can setup email and calendar co-existence between your Google Workspace and Microsoft 365 tenants , which is particularly useful for organisations who are looking to use both the platforms or are in process of migrating from one to another.</p><p>In my experience with Google Workspace enterprise customers’s most of the clients moving to google still prefer to leverage Azure AD as their Identity and access management solution because it already enables access to large number of LOB applications and give’s them capabilities like conditional access , mobile device and endpoint management capabilities which are limited in google’s cloud identity platform.</p><p>In this blog we will look at how Azure AD can be leveraged as Idp for Google Workspace services like Gmail, Drive , Docs ,Sites etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*YWwNr31BbpX11a5-GcUw8g.png" /></figure><p>Pre -requisites :</p><ol><li>Azure AD Tenant with your google domain added and verified.</li><li>Google Cloud / G Suite Connector by Microsoft single sign-on (SSO) enabled in Azure AD. This is the connector by Microsoft which enables automated user provisioning to google cloud identity and single sign on for google.</li><li>Decision on what all objects you want to provision from Azure AD to Google tenant such as users , groups or both.</li></ol><h3>Add Google Cloud / G Suite Connector by Microsoft to Enterprise Applications.</h3><p>To configure the integration of Google Cloud / G Suite Connector by Microsoft into Azure AD, you need to add Google Cloud / G Suite Connector by Microsoft from the Azure gallery to your list of enterprise applications.</p><ol><li>Sign in to the Azure portal azure.microsoft.com</li><li>On the left navigation pane, select the Azure Active Directory service.</li><li>Navigate to Add and click on Enterprise Application</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*kmWzE2Wudl9jwVTnEsJahw.png" /></figure><p>4. In the Add from the gallery section, type Google Cloud / G Suite Connector by Microsoft in the search box.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/689/1*r9i2x1KmMblCsF3iUo2LzA.png" /></figure><p>5. Select Google Cloud / G Suite Connector by Microsoft from results panel and then click on create. Wait a few seconds while the app is added to your tenant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*FOnJGshpFOz7mLSTDyY2cA.png" /></figure><p>Once the application is added it will be visible in the list of Enterprise Applications for your organisation and you can modify the app properties as below :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*IUG0XUyeAl4mjOnLHHeGxQ.png" /></figure><p><strong>Assign Users and Groups</strong></p><p>Now for you be able to provision users in google admin console and they be able to authenticate via Azure AD you need to assign users to this connector so that it can be created in google tenant. (this setting is defined in the connector properties while configuring it see above screenshot). This provides you the flexibility of only assigning those users to the app who will be using google services .</p><p>Go to Enterprise applications → Google cloud /G Suite connector by Microsoft → Users and groups</p><p>Here you can add the users and groups which you want to assign to this app for sync to google workspace.For this demo i have just manually assigned one user to the application as below :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4OvLqeOOXMvuu138aocKew.png" /></figure><p><strong>Configure Automated User Provisioning to Cloud Identity.</strong></p><p>After adding the connector , we need to need the automate user provisioning from Azure ID to Google Cloud Identity first.</p><ol><li>Go to the Enterprise Application page → Google cloud/G Suite connector by Microsoft → Provisioning → Get Started</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vGvlF3OICDIkRMgWnkE8Zw.png" /></figure><p>2. Select Automatic or Manual. We will go with Automatic</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*-dYBPUEQfLCtJjZ167q7_g.png" /></figure><p>3. Click on Authorise and provide your google tenant admin credentials .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*hVTiW_nGXzZ4LKdtXvkbtg.png" /></figure><p>4. Configure Mappings : what all data you want to flow from Azure AD to Google. For our tutorial i have selected Users only. ( So users which we earlier assigned to our app will get created in google ).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/1*VNK1IgGDBtTmI7CPCFwIVw.png" /></figure><p>5. You can also define which attributes you want to sync from your Azure Directory into Google user profile’s as below :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/742/1*JdnLjiQDEoCUGVLTarNjCA.png" /></figure><p>6. Also you can add new attribute mapping or customise the existing one. like i have customised one attribute mapping to create users in a particular OU in google as below :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JcKBA2pMnUExF_CcqwYFGA.png" /></figure><p>7. Now once the provisioning is done let’s look into the Google console where the object is created :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q6TjJxTyLC_R62c2NMYHBA.png" /></figure><p>8. This connector gives you option to manage your provisioning settings such as restart provisioning , provisioning on demand, provisioning logs to troubleshoot any issues related to user creation , deletion or updation.</p><p>Path : Enterprise Applications → Google Cloud/G Suite Connector by Microsoft →Provisioning</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/946/1*rB36E79nTqwVV_KrO3mqfw.png" /></figure><p><strong>Setting Up SSO for Google Services</strong></p><p>Now once you have configured Automated User provisioning , we will set up SSO so that users can login into google services using AAD as their IDP.</p><ol><li>In the Azure portal, on the Google Cloud / G Suite Connector by Microsoft application integration page, find the Manage section and select single sign-on ,select SAML .</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gig93zNeb26LmMoTSJwCYA.png" /></figure><p>2. On the set up single sign-on with SAML page perform below steps :</p><p>On the Basic SAML Configuration section click pencil button to configure below URL’s :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/1*nzM19dNwWPWUu_e55AUldg.png" /></figure><p>a. In the Identifier text box, type a URL using one of the following patterns:</p><p>google.com/a/&lt;yourdomain.com&gt;</p><p>google.com , https://google.com</p><p>https://google.com/a/&lt;yourdomain.com&gt;</p><p>b. In the Reply URL text box, type a URL using one of the following patterns:</p><p><a href="https://www.google.com/acs">https://www.google.com/acs</a></p><p>https://www.google.com/a/&lt;yourdomain.com&gt;/acs</p><p>c. In the Sign on URL text box, type a URL using the following pattern: https://www.google.com/a/&lt;yourdomain.com&gt;/ServiceLogin?continue=https://mail.google.com</p><p>Note : if you are enabling using domain specific issuer ( i.e user login in using url such as mail.google.com/a/&lt;yourdomain.com&gt; )option in Google admin console then you must add google.com/a/&lt;yourdomain.com&gt; url in identifier otherwise it is not required.</p><p>3. Google Cloud / G Suite Connector by Microsoft application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration . The default value of Unique User Identifier is user.userprincipalname . We will leave this setting unchanged.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*wBiKd4O3h2ZrCJ7TmjCrAA.png" /></figure><p>4. In the SAML Signing Certificate section, find Certificate (Base64) and select Download to download the certificate and save it on your computer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*HT2qHpchPfUaNNElPl9Z7w.png" /></figure><p>5. On the Set up Google Cloud / G Suite Connector by Microsoft section, copy the appropriate URL(s) based on your requirement and add them in your google admin console.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/577/1*euAWYa-tPf0oQ2o5zrRp8w.png" /></figure><p>6. Google has given admins the ability to configure authentication through a third-party identity provider for a long time . In 2021, this capability was expanded by making it possible to choose between third-party identity provider or Google authentication for specific groups or organisational units (OUs).</p><p>Now, you can further customize authentication by setting up single sign-on (SSO) profiles for multiple identity providers and then configuring authentication for each group or OU . This gives you a flexibility to use multiple Idps for your users . In this blog we will configure Azure AD as IDP for whole organisation and use a single SSO profile for whole organisation.</p><p>Now , login to Google admin console → Security → SSO with Third party IDP to configure the URL copied from Azure portal in previous step(step 5) and upload the certificate you downloaded to your computer in step 4 and click save.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eK0FoOUUHSahzZH9Zl2FiA.png" /></figure><p>Note : If you check on domain-specific issuer you need to add appropriate URL in the SAML configuration while configuring SSO settings in azure portal.</p><p>Test your configuration :</p><ol><li>Go to accounts.google.com→ sign in → enter your google username</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*ZV26IdnU4x9CMIL_4vL3Tw.png" /></figure><p>You will be now redirected to Microsoft Login page :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*lvAhzbBAHae7kwoZfxnSJQ.png" /></figure><p>Enter your login id and password and you will have access to your Google workspace services.</p><p>This is how you can co-exist your identities with Azure AD and Google tenant’s and at same time use Azure AD as your identity provider. Hope you enjoyed reading it. Thanks</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2c8508c39ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rising Mergers and Acquisition among Google Cloud Partners]]></title>
            <link>https://medium.com/@mittal.saurabh89/rising-mergers-and-acquisition-among-google-cloud-partners-44f1992116b4?source=rss-63c014d33590------2</link>
            <guid isPermaLink="false">https://medium.com/p/44f1992116b4</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[mergers-and-acquisitions]]></category>
            <dc:creator><![CDATA[Mittal Saurabh]]></dc:creator>
            <pubDate>Wed, 13 Apr 2022 09:55:12 GMT</pubDate>
            <atom:updated>2022-04-13T09:55:12.007Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/606/0*Ddp4Bc9HD3hAqd-W.jpg" /></figure><p>Hyper scalar industry’s 3rd biggest cloud service provider, Google Cloud has been growing pretty well over the past couple of years trying to catch up with the leading public cloud providers in the market AWS and Azure . Google cloud currently holds 9 % of the market share whereas AWS sits at distant top with approx. one-third of the total market and with Azure having 22 % of market share. Google Cloud revenue increased 47% for the full year 2021 versus 2020.This growth has been fuelled ever since Thomas Kurein joined as CEO of Google cloud in 2018 . Their has been a significant strategic shift from technology &amp; engineering to focusing on client servicing and strategic partnerships with clients &amp; partners. This has allowed Google to expand it’s market to old school enterprise accounts apart from new-age startup and digital native companies which were until 2018 main customers for GCP.</p><p>Also Google’s Go to Market approach for Google cloud is also evolving , which is now increasingly becoming partner first , partner led where Google’s aim is to equip it’s channel partners to drive consumption and services business . Till recently , google partner ecosystem was built majorly by small and regional partners focussing on specialisation in area of Infra , Data , App modernisation , AI &amp; ML with revenue coming from consulting , migration and development services but with recent growth of Google cloud and the partner first led approach Global system integrators are also looking to get the share of the pie by bringing their deep rooted expertise of offering end to end managed services for some of the largest enterprise customers across the globe , where google cloud is looking to make new inroads. Hence Google’s partner first approach will see global system integrators playing a pivotal role in not only helping google acquire large traditional enterprise as customers but also build a large workforce trained on GCP and help google achieve it’s goal of equipping more then 40 million people with cloud skills .</p><p>This approach has led to significant increase in number of strategic partnerships which Google has done with Global system integrators to drive market share and revenue in recent past. In recent time it can be seen that almost every global and mid-sized system integrators have announced their strategic alliance with Google to offer GCP services. With a order backlog of $50 billion dollars , it presents an immense opportunity for GSI and Google partners to scale up their capabilities on GCP to capture this market for their consulting , migration and managed services business and also build industry specific solutions for their customer to cater the increasing demand for Google Cloud .</p><p>Google is also ramping up investments in partner ecosystem. The areas of investment cover’s partner incentives including migration, co-marketing, training and enablement of people, and co-innovation funds for building industry led vertical solutions offerings on Google cloud in areas such as 5G , AI/ML , Data and App modernisation.</p><p>To tap this growing Google cloud market partners are faced with two options either they build their capabilities and specialisations on GCP organically from scratch or inorganically acquire these skills by way of M&amp;A . Acquisition are good way to quickly build and expand tech capabilities on Google cloud ( Infrastructure Migration , App Modernisation and niche areas like Data, AI &amp; ML ) resulting in quicker go to market programs for their services and industry solutions. They also help them attain solution specific specialisations on Google cloud.</p><p>It is interesting to see the intent and goal of Global System integration for acquiring a regional or mid sized google cloud partner , specialising in areas of Infrastructure , App Modernisation , Data ,AI &amp; ML. M&amp;A gives them the ability to quickly acquire tech capabilities in these niche areas , access to highly skilled talent and access to client in a geography , vertical or technology domain where otherwise they had no or limited presence. Organically building these capabilities requires huge investment and effort in ramping up hiring , re-skill/up-skill existing resources and setting up the sales engine to bring new clients. But with an acquisition these SI can focus on creating service offerings based on Google Cloud which they can quickly take to client’s with a delivery engine already now in place .</p><p>On the other hand for companies like SADA acquiring an Indian based Google Cloud partner provides them capabilities to quickly setup their delivery centre’s in India hence allowing them to offer services to their North American clients at more competitive prices hence giving them ability to compete with GSI’s as well .</p><p>Let us look at some of the most recent acquisition’s</p><ol><li><strong>Persistent System announced acquisition of MediaAgility</strong> , a Google cloud Premier partner on March 14, 2022 to create a Google Business Unit for $74 Million Dollars , with this acquisition Persistent will get access to MediaAgility 500+ people strong workforce .This acquisition is strategically seen as move by to leverage MediaAgility’s expertise in Google cloud to significantly expand Persistent’s ability to execute cloud-based digital transformation journeys for it’s global clients.</li><li><strong>SADA acquires ByteWave Digital</strong> :On 16,2021 SADA announced acquisition of Byte Wave Digital , a Google Cloud Partner committed to providing innovative and scalable technology solutions and services to help businesses of all sizes unlock the power of the cloud. ByteWave Digital maintains its global delivery centre in Thiruvananthapuram and Pune, India. With this acquisition, SADA will expand its business into the APAC market and add approximately fifty technical experts to SADA’s global team, furthering its promise to put Google Cloud to work for its customers across the globe. As a fully-owned subsidiary of SADA, ByteWave Digital will become SADA India, integrating its professional services, engineering, and support for 24-hour assistance to qualified customers worldwide.</li><li><strong>Xebia acquires g-company for €24 million</strong> . Dutch IT consultancy Xebia has acquired Google Cloud Premier Partner g-company for €24 million. With this acquisition, Xebia hopes to increase its GCP (Google Cloud Platform) capabilities and expands its services with solutions like Google Workspace. After the acquisition, g-company and Xebia will remain a Google Cloud Premier Partner and Authorised Google Cloud Training Partner, including a shared infrastructure and workspace competency. g-company will continue to operate under its own label The acquisition will be signified by adding “proudly part of Xebia” to the company logo.</li><li><strong>Accenture completed the acquisition of Wabion</strong> on 2nd September 2021 ,Wabion a Google Cloud services boutique with headquarters in Esslingen, Germany and Olten, Switzerland as well as additional offices in Munich, Cologne and Lausanne. Wabion is a Google Cloud Premier partner and well recognized for its deep expertise of Google Cloud innovations and technological developments. The team of more than 60 professionals will join Accenture Google Cloud Business Group.</li></ol><p><strong>In Summary</strong></p><p>This increasing trend of M&amp;A will may result in consolidation of Google partner ecosystem with smaller partner getting acquired by larger ones in a bid to quickly capture the market and emergence of select few larger players in form of Global System Integrators catering to needs of large enterprise customers in areas of managed services and emergence of few selected boutique firms offerings very specialised services in niche technology areas.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44f1992116b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[{Part 2}Two Part Series on Google Workspace and O365 Mail and Calendar Co-existence]]></title>
            <link>https://medium.com/@mittal.saurabh89/part-2-two-part-series-on-google-workspace-and-o365-mail-and-calendar-co-existence-c28742faaea5?source=rss-63c014d33590------2</link>
            <guid isPermaLink="false">https://medium.com/p/c28742faaea5</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[coexistence]]></category>
            <category><![CDATA[m365]]></category>
            <category><![CDATA[g-suite]]></category>
            <dc:creator><![CDATA[Mittal Saurabh]]></dc:creator>
            <pubDate>Wed, 20 Oct 2021 06:25:03 GMT</pubDate>
            <atom:updated>2022-04-22T18:26:06.492Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Part 2: Co-existence : Setting up Calendar co-existence between Google Workspace and M365.</strong></p><p>In the <a href="https://medium.com/p/3f2a89b695c4/edit">Part 1 </a>of my co-existence series i had talked about mail flow co-existence when you are migrating from O365 to Google Workspace or setting up a Hybrid environment where some users are using O365 and others Google Workspace.</p><p>In this part 2 of my co-existence series I will talk about another important co-existence setup which allows user to see free/busy information .</p><p>Google provides a tool called Calendar Interop for administrator which they can use to allow Microsoft Exchange and Google Calendar to work together. Users in both systems share their availability status so everyone can view each others’ schedules.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*8LrHH5yV256Igk3e97LccQ.png" /><figcaption>Calendar interop</figcaption></figure><p>With this tool admins can :</p><ul><li>Turn on Calendar Interop for a domain.</li><li>Allow Calendar users to book Exchange calendar resources, such as meeting rooms, when they schedule a meeting.</li><li>Use automated tools to verify setup.</li><li>View error messages and suggestions for resolving those errors.</li><li>Track cross-system user requests for availability information in the Google Admin console.</li></ul><h3>Calendar and Exchange users can</h3><ul><li>View each other’s availability information. Availability (only busy blocks are visible to users) and additional event information (titles and locations of events are visible to users) lookups are supported.</li><li>Important: Calendar Interop respects event-level privacy settings. If an event is marked as private in Exchange, the event’s details are not visible in Google Calendar. Similarly, if an event is marked as private in Google Calendar, its details are not visible in Exchange.</li><li>View availability and additional event information of Exchange calendar resources (such as meeting rooms), and also book resources when they create events in Google Calendar.</li><li>Use Calendar Interop with Google Calendar on Android, Apple iOS, and web clients.</li><li>Use Calendar Interop with Microsoft Exchange 2013 or 2016, or Exchange Online (Office 365) clients (including computer, mobile, and web Outlook versions.</li></ul><p>In this blog series I will be showing how Calendar Interop can be setup between Google Workspace and Exchange Online Users , when they are sharing the same domain namespace.</p><p>Calendar Interop System Requirements :</p><ul><li>Exchange Online (Office 365) subscription , if you remember we have already setup the tenants , domains and the users in the part 1 of this series. ( It is important that you go through the Part 1 to understand the setup)</li><li>An exchange role account Google Calendar uses to access Exchange.</li><li>A google role account Exchange uses to access Google Calendar.</li><li>A single Exchange endpoint for availability information.</li><li>Alias domain in Google Workspace , if your Microsoft Exchange and Google Workspace users have overlapping email addresses (for example, the email domain is @yourdomain.com for both Google Workspace and Exchange online users). Exchange decides where to direct availability requests based on the domain name. There’s a conflict if the domain name used on Exchange online for Google Workspace users is the same as the domain used by Exchange online users. Hence we need to use user alias domain to make sure the availability address space points to Google Workspace, not Exchange online. Hence in our case we will be using the alias domain which is provided by google by default .</li></ul><p>Now let us setup , both exchange online and Google workspace to enable calendar co-existence between the two environment for the users</p><p><strong>Allow Google Calendar user to view Exchange Online users data</strong></p><p>Step 1 : Setup Exchange Users</p><ol><li>Make sure each Exchange user has an Exchange account with an associated mailbox in our case we have nonmigrateduser@yourdomain.com created in O365 with mailbox.</li><li>Make sure each Exchange user satisfies one of the following requirements:</li></ol><ul><li>No Google Workspace account.</li><li>A Google Workspace account with <a href="https://support.google.com/a/answer/6002940">Google Calendar turned off</a> , in our case we have nonmigrateduser@yourdomain.com created in Non-Migrated OU and for this OU calendar Service is turned off.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*VZ_4rQS4j8WrpcQYj16yoA.png" /></figure><p>Step 2 : Create a Exchange role account</p><p>Create an Exchange online role account with the Exchange recipient type set as a user mailbox account. See below , this is a normal account without any admin privileges , you can see i have assigned a M365 E5 license but you can just enable exchange online license as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/943/1*8IjR0_dS5yxq0csPuHbkBA.png" /></figure><p>The Exchange online role account is only used for availability lookups. Google Calendar uses the account to authenticate with your Exchange server to find availability details of Exchange users. For events to be visible to Google Calendar users, events must be shared with this role account.</p><p>Step 3 : (OAuth 2.0 for Exchange Online only) Application set up in the Microsoft Azure portal</p><p>To use OAuth 2.0 as your authentication method for Exchange Online; you need to apply several settings to your setup in the Microsoft Azure portal. Follow these steps to set up your instance.</p><ol><li>Register the application in the Azure portal by following these steps under Azure Portal → Azure Active Directory → App Registration → New Registration</li></ol><ul><li>Give the display name for your app</li><li>Supported accounts type : Use the first Option</li><li>Leave rest at default → Register</li></ul><p>Notes:</p><ul><li>Leave the Supported account types and Redirect URI values at their default settings.</li><li>Save the Application (client) ID as you’ll need it later to set up OAuth 2.0 authentication in Google Workspace.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/909/1*am5S38cp7QVqzwmB4MFcjQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dJEQzWxBAZ-DiQucZn7OYg.png" /></figure><p>2. Add a client secret to set the application’s credentials by following these steps under “Add a client secret” :</p><p>Azure Portal → Azure Active Directory → App Registrations → Google Calendar Interop ( the app you added now) → Clients and Certificates → Add Client Secret → Give description &amp; expiry time → Add</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/579/1*oiMhqKNg04iBmFuTo4de_Q.png" /></figure><p>Save the value of the client secret , because it will not be shown again and it will be required later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B3v9nZTAbSqyphWtytW0Hg.png" /></figure><p>3. Add API permissions to your registered application by following these steps under “Add permissions to access your web API” as below in your app :</p><ul><li>On the “Request API permissions” page, click the “APIs my organisation uses” tab and search for “Office 365 Exchange Online”.</li><li>Click “Office 365 Exchange Online”</li><li>“Application permissions”.</li><li>Check the “full_access_as_app” box to set the application permissions.</li><li>Add Permission</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V5WHjGrpTdDXHok9e3kJtw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/857/1*ifD4oTnmczeOjb8IYmZ17w.png" /></figure><p>3. Click the admin consent button for your tenant so the permissions take effect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AY93klLn9WNxhI_NRUynyw.png" /></figure><p>Post Granting permission it will show as “ Granted for your <strong>Directory</strong>”</p><p>4. Locate the OAuth 2.0 token endpoint (v2)</p><p>Besides the Application (client) ID and the client secret, you also need to know your OAuth 2.0 token endpoint. The endpoint looks like this :</p><p>https://login.microsoftonline.com/<em>{tenant}</em>/oauth2/v2.0/token</p><p>Azure Portal → Azure Active Directory → App Registration → Endpoints</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9KH2YduWKo5eJVoj6Z_PJg.png" /></figure><p>Setup Google admin console :</p><ol><li><a href="https://admin.google.com/">Sign in</a> to your <strong>Google Admin console</strong>.</li><li>From the Admin console Home page, go to Apps → Google Workspace →Calendar.</li><li>Click Calendar Interop management.</li><li>Check the Enable Interoperability for Calendar box.</li><li>Under Type, select Exchange Web Services (EWS).</li></ol><ul><li>Under Exchange Web Services URL, enter the URL of the default Exchange Web Services URL for exchange online , your EWS server URL is most likely <a href="https://outlook.office365.com/EWS/Exchange.asmx">https://outlook.office365.com/EWS/Exchange.asmx</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S8Mzy1dAp8nqjEpCe6JsSg.png" /></figure><p>6. Under Exchange Role Account, enter the primary SMTP address of the Exchange role account in the username@yourdomain.com format which was created in Exchange online interoproleaccount@yourdomain.com ( see above)</p><p>7. Select your authentication method: OAuth 2.0 client credentials.</p><ul><li>When using OAuth 2.0 for Exchange Online, follow these steps:</li><li>Under Token endpoint URL, enter the OAuth 2.0 token endpoint URL from your Azure tenant.</li><li>Under Application (client) ID, enter the Application ID assigned to your app during app registration.</li><li>Under Client secret, enter the value from the client secret assigned to your app during app registration.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/867/1*8V6wj-cnSPXeJq65OG-EFA.png" /></figure><p>8. Leave rest of the settings to default.</p><p>9. Click Save</p><p><strong>Allow Exchange Online Users view Google calendar available data.</strong></p><p>Step 1 : Setup Google Workspace Users, Ensure that each of your google workspace user has following</p><p>If you remember in our Google Workspace setup in Part 1 , we had created 2 users migrateduser@yourdomain.com and nonmigrateduser@yourdomain.com ( Part of Non-Migrated OU) .</p><ol><li>Now as part of Calendar Interop setup you need to ensure that those users who are using their Google accounts have their Google Calendar service turned on , So in our case migrateduser@yourdomain.com which is live on Google Workspace must have calendar service turned on.</li></ol><p>2. Each Google Workspace user must have a mail contact in exchange online. This helps Exchange Online retrieve availability information from Google.So we have already created a Mail contact for the migrateuser@yourdomain.com as below . As mentioned since the user share the same domain namespace in both Exchange online and Google workspace we will use a domain alias which will help look up availability of Google Calendar user, that is why the contact has external address as below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/659/1*pcDdSdBMaWQ8pzS1Npeahg.png" /></figure><p>3. Ensures the mail contact appears in the Exchange Online Global Address with the primary smtp address as migrateduser@yourdomain.com so that users in Exchange online can easily find the user in GAL and the alias domain email address should be added as external email address.</p><p>4. Also ensure that mail sent to alias domain id is delivered to the user mailbox.( Remember we already tested this in our email -coexistence)</p><p>Step 2 : Create a Google role account</p><p>This is the Google role account and is used by Exchange to access Google Calendar users’ availability information.or events to be visible to Exchange users, events must be shared with the Google role account.</p><p>Turn on Calendar for this account and ensure it has either free/busy or event detail access to check availability for all domain users.</p><p>after this generate the exchange credentials using the <a href="https://calendar.google.com/Exchange/tools/">Exchange authentication credential generation</a> tool provided by Google. I have used my super admin account to generate this credentials but you can use a normal google user as a role account without having any admin rights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ilVI4B1N5AjAs4IbgTbBIQ.png" /><figcaption>Click on Execute</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PgU5UqxXI567_DL_I2NLZQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/505/1*uvzg1jOrv6S8uQkLWdjYCA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BSM_45TTQVIyJ5tXa4SAWQ.png" /></figure><p>Click Download to get the generated credentials. Save the credentials, as you’ll need them to add the availability address space to Exchange.</p><p>Step 3 : Add an availability address space to Exchange Online.</p><p>Google Calendar must be added as an availability address space in Exchange Online to allow Exchange Online to query Google Workspace for the mail contacts you set up earlier.</p><p>For each Google Workspace domain, you need to run several commands in Exchange Online PowerShell . When you run commands, you need to set certain parameters. The configuration tool provides PowerShell code with the parameters required.</p><h4>Add the availability address space</h4><p><em>You must be signed in as a super administrator for this task.</em></p><ol><li>Open the <a href="https://calendar.google.com/Exchange/tools/">Exchange server configuration</a> tool. Click on Exchange Server configuration.</li><li>Upload the credential file for the Google role account you generated in the previous step.</li><li>Select the Exchange server version option you’re configuring.</li><li>Specify the email of the local account on Exchange that Google Calendar can use to make organisation wide free/busy requests to Exchange. These requests allow Google Calendar to get free/busy information of any account on Exchange within the organisation. For example, interoproleaccount@yourdomain.com (the local account email address should be the Exchange role account)</li><li>Specify the Google availability address space you wish to add to Exchange. This will be the domain of your Google Workspace tenant , since in our case we are using the alias domain for this purpose , we will use the alias domain which is yourdomain.com.test-google-a.com</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*4gKDaXdzch6s46VzXJaWpg.png" /></figure><p>6. Click Show Exchange setup.</p><p>The tool generates both Exchange server settings and a fragment of PowerShell code that can be pasted into Exchange Server PowerShell to configure the availability address space of your Exchange server.</p><p>7. Connect to Exchange online powershell and run the powershell cmdlt generated above. Sample code is something like this :</p><pre>if ((Get-AvailabilityConfig) -ne $null) {<br>Set-AvailabilityConfig -OrgWideAccount <a href="/service/mailto:interoproleaccount@crafthub.co.in">interoproleaccount@</a>yourdomain.com;<br>} else {<br>New-AvailabilityConfig -OrgWideAccount <a href="/service/mailto:interoproleaccount@crafthub.co.in">interoproleaccount@</a>yourdomain..com;<br>}<br>$password = echo &#39;PHHMvH9Tj4pA4UH4Lyf6AgkadVt7dDfCvAHFXl_Xdsv52u1AZSkILoCdRN0Nlrx4&#39; | ConvertTo-SecureString -asPlainText -force;<br>$credentials = New-Object System.Management.Automation.PSCredential -argumentList &#39;yourdomain.com\admin&#39;, $password;<br>Remove-AvailabilityAddressSpace yourdomain.test-google-a.com -ErrorAction SilentlyContinue -Confirm:$false;<br>Add-AvailabilityAddressSpace -forestName yourdomain.test-google-a.com -accessMethod orgwidefb -credentials $credentials -targetAutodiscoverEPR https://calendar.google.com/autodiscover/autodiscover.xml</pre><p>The result will be as below :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*hmNCXHICuE0WksPyPRgIIw.png" /></figure><p>8. Test Free / busy</p><p>Now as the setup is complete , lets test it :</p><ol><li>Sign in to a Google Workspace account, create a Google Calendar event, and enter the email address of a Microsoft Exchange user ( nonmigrateduser@yourdomain.com) to invite them.</li><li>The Exchange user’s availability status should be visible.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b6bHoy50Qo5BMoGaDMWBGQ.png" /><figcaption>Free/busy status is available for the Non-Migrated user</figcaption></figure><p>3. Similarly now login to Exchange Online mailbox of the non-migrated user and setup a meeting invite with the Google Workspace user (migrateduser@yourdomain.com). The google calendar status will be visible :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9oI4y16XThYFuYn8PLOjqA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c28742faaea5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[{Part 1}Two Part Series on Google Workspace and O365 Mail and Calendar Co-existence]]></title>
            <link>https://medium.com/@mittal.saurabh89/part-1-two-part-series-on-google-workspace-and-o365-mail-and-calendar-co-existence-3f2a89b695c4?source=rss-63c014d33590------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f2a89b695c4</guid>
            <category><![CDATA[coexistence]]></category>
            <category><![CDATA[office-365]]></category>
            <category><![CDATA[g-suite]]></category>
            <category><![CDATA[google-workspace]]></category>
            <category><![CDATA[microsoft-365]]></category>
            <dc:creator><![CDATA[Mittal Saurabh]]></dc:creator>
            <pubDate>Sun, 19 Sep 2021 13:49:00 GMT</pubDate>
            <atom:updated>2022-04-22T18:20:36.956Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Part 1 : Co-existence : Setting up email co-existence between Google Workspace and M365.</strong></p><p>Google Workspace and O365 are among two most popular enterprise productivity and collaboration available to enterprises and you will find that most organisations are using these one of these platform for their users’s productivity and collaboration needs. In this era of pandemic where remote work has become a norm and also companies offering users a solution of their liking it is not uncommon to find organisations which are using both of these solutions :</p><ol><li>O365 and Google Workspace in a Hybrid mode where some users are using O365 and others are on Google workspace</li><li>Organization migrating from O365 to Google workspace and want to setup co-existence for email and calendar during the migration phase.</li><li>Setup Calendar Free busy with external partner’s.</li></ol><p>In this Part 1 I will show you how we can set up email mail flow co-existence when we are migrating from O365 to Google Workspace.</p><p>Overview of setup Environment for this demo :</p><ol><li>O365 tenant with E5 license ( license can be as per your environment whatever you are using) with custom domain added .</li><li>Google Workspace tenant setup with the primary domain same as the custom domain added in O365 and we will be using the google provided alias domain.</li><li>MX Records pointed to O365 , so all email are routed via Exchange Online.</li><li>Currently we are assuming that this is a cloud native setup , if required you can also setup Azure AD for user provisioning in Google and as an IDP for Single sign on for Google users.</li></ol><p>Now let us look at the pre — requisite and prepare the two tenants :</p><p>Preparing the tenants O365 and GW :</p><ol><li>I am assuming that you have already setup your O365 tenant and verified your custom domain .</li></ol><p>AdminPortal → Home → Domains</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/607/1*U3hQk7JjizZ2yAFFcI-hKA.png" /><figcaption>Domain to be added in O365 and Verified.</figcaption></figure><ol><li>Once you are done with this we will create the below 1 Mailbox in O365 with a name nonmigrateduser@yourdomain.com</li><li>Mail contact migrateduser@yourdomain.com with external email address as migrateduser@Yourdomain.test.google-a.com</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/659/1*pcDdSdBMaWQ8pzS1Npeahg.png" /></figure><p>3. MX records are pointed to Exchange online</p><p>Preparing the Google Workspace Tenant :</p><ol><li>I am assuming you have your google workspace tenant setup with primary domain as yourdomain.com , your domains will look like below picture, in this demo i am using the alias domain provided by google itself but you can add your custom domain as a secondary domain and make it a alias :</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*09gMfcTIzb54kM99IR5PSQ.png" /></figure><ol><li>Now, Add two users nonmigrateduser@yourdomain.com and migrateduser@domain.com in Google Workspace ( We will need all the user which are their in our O365 domain to be provisioned in Google for GAL lookups even if user is still using their O365 account, if required you may not assign a license to the user in Google workspace who are not yet live on Google)</li><li>Create a OU ( Non- Migrated) where non-migrated user will be placed and turn the calendar service off for this OU ( i will explain later the reason for this in Part 2)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*fD-C1Cs3UXt6pMmNQOgwjg.png" /><figcaption>OU structure in GW</figcaption></figure><ol><li>Create a host for routing intra-domain mails from google workspace /migrated user to non-migrated user which are still using O365 account.</li></ol><p>For Creating a host in admin console go to Apps → Google Workspace →Settings for Gmail → Hosts → Add Route &amp; save</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*92yiMys7UEp-TcBh26J4QQ.png" /><figcaption>Add Host in Google Workspace</figcaption></figure><ul><li>Add a Routing rule for Non- Migrated OU as below :</li></ul><p>Apps → Google Workspace →Settings for Gmail → Routing → Add Rule &amp; Save</p><p>Ensure you add this rule for your Non-Migrated OU</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*F_-7F0N2jJ7MncKkY0W1mA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*tlY7qXAi0nB1uS6-MHePSw.png" /><figcaption>Select the Host as O365.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*7iQvR2UXyfdDeUm9rYntqA.png" /></figure><p>Mail Co-existence flow will look like this :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*VeiC9Dqzt-_jPw4O_lF9ew.png" /></figure><ol><li>Users with mailbox active in O365 (Non- Migrated) will directly access O365 account for sending and receiving emails .</li><li>Intra domain email routing in O365 : if a O365 user( non-migrated) sends internal mail to migrated user it will be delivered to his GW account via the mail contact in O365 which forwards the mail to an external email address of the user in Google workspace ( Migrated user) . This external address will be a secondary smtp address ( alias ) of the user in Google workspace.</li><li>Intra domain email routing in Google workspace : When a Google workspace user ( migrated user) sends a mail to a user in O365 ( non migrated) the mail flow will use the routing rule created above. Any intra domain mail sent to a user in the non migrated OU will come under the preview of this rule and mail sent to those users will be delivered to their corresponding mailbox in O365.</li><li>Users with mailbox (migrated user) active in Google workspace will directly access their Google account and send mail directly and receive mail forwarded by the migrated user mail contact in O365.</li></ol><p>This is how the mail Co-existence work between O365 and Google Workspace. Please let me know feedback in comments and if you have any query please reach out to me. I will post the next part of this post soon on calendar co-existence soon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f2a89b695c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automating Shared Mailbox Creation in Exchange Online using Power Automate and Azure Automation]]></title>
            <link>https://medium.com/@mittal.saurabh89/automating-task-in-exchange-online-using-azure-automation-ad8e9382c25b?source=rss-63c014d33590------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad8e9382c25b</guid>
            <category><![CDATA[m365]]></category>
            <category><![CDATA[exchange-online]]></category>
            <category><![CDATA[microsoft-power-automate]]></category>
            <category><![CDATA[workflow-automation]]></category>
            <category><![CDATA[azure-automation]]></category>
            <dc:creator><![CDATA[Mittal Saurabh]]></dc:creator>
            <pubDate>Sun, 15 Aug 2021 16:44:06 GMT</pubDate>
            <atom:updated>2021-08-15T16:47:21.295Z</atom:updated>
            <content:encoded><![CDATA[<p>Introduction</p><p>Exchange online administrators today are looking for new ways to automate routine tasks for managing their M365 subscription and provider users more options to self service , provide service at a click to cater their request automatically .</p><p>In this article i intend to demonstrate how admin’s can leverage M365 services to automate business process /IT processes using below services</p><p>Azure Automation</p><p>Microsoft Power Automate</p><p>Sharepoint Online</p><p><strong>The Scenario</strong></p><p>SharedMailbox ‘s are very commonly used type of mailbox in Microsoft exchange and accessed by business users for their various day to day jobs and sending emails via them. Usually Exchange online admins are responsible for creating the mailbox on per request basis and provide full access, send as or send on behalf permissions to user as required. In this blog post i will demonstrate a simple workflow created in Power Automate which automates the entire process of shared mailbox creation &amp; granting full access permission to the requestor in Exchange Online. The entire flow is created in Power Automate will look like this along with technologies used in each step:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/0*N4z18bfuMy4NVTGz" /><figcaption>Requirement</figcaption></figure><p><strong>Azure Automation</strong></p><p>Azure Automation is a “serverless” environment you can use to run PowerShell scripts in the cloud. For example, when running scripts in the Azure Automation environment, you can scale up or down Azure VMs, you can manage your on-premises servers without exposing your servers to the internet, managing your Office 365 tenant and more.</p><p>Provision Azure Automation Accounts :</p><ol><li><strong>Create Azure Automation Account</strong></li></ol><p>Click on Create to create a new automation account.</p><p>– Login to portal.azure.com → Search Automation accounts → Create<br>– Give your automation account a name ( ExchangeAutomation in our case)<br>– Select your subscription (free trial or pay-as-you-go)<br>– Create or select a resource group , if group doesn’t exit you can create one at this step itself.<strong>( RG-AA) <br></strong>– Location <strong>( East US2)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0wRx_97GAJicjcwh.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HV3vr9DtmwCjY3Ns" /><figcaption>Automation Account Page</figcaption></figure><p><strong>2. Import required modules if necessary</strong></p><p>Go to your Azure Automation account → Module → Browse Gallery and Install below modules :</p><p>– AzureAD<br>– ExchangeOnlineManagement</p><p><strong>3. Add Service Account: </strong>I<strong> </strong>have used dedicated account in O365 with Global admin rights, but you can use a account with exchange management rights as well and no MFA ( Note : if MFA is enabled for your account then your runbook may not work, so please disable)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*hlm1q09gDFbvkVZ6_g4Yzw.png" /><figcaption>Credentials Creation</figcaption></figure><p><strong>4. Create a Runbook</strong></p><p>In your Azure Automation account you will find runbooks. There are a couple of Tutorial runbooks already in your account, but we are going to create two new one.</p><ol><li>Click on Create a runbook . In this we will create 2 runbooks one for sharedmailbox creation and full access</li><li>Give your runbook a meaningful name like mine is SharedMailbox and Full access respectively.</li><li>Select PowerShell for runbook type and maybe a description that describes what the runbook does.</li><li>Click on Create</li><li>Create another runbook using same method for full access rights.</li></ol><p>Your runbook is basically a blank PowerShell script. On the left side you will find an overview of available CMDLets, a list of your runbooks (you can trigger other runbooks from within your runbook) and assets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uvL3lD85HrbqRSc2" /><figcaption>Runbooks in Automation accounts</figcaption></figure><p>To create a shared mailbox and provide full access permissions we are going to connect to Exchange Online. To do this we will need the Azure Run As Connection and the credentials which we created “<strong>sm</strong>” in my case.</p><p>The script for sharedmailbox creation runbook is as below :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/763/0*c983nzZsyoXzHKmQ" /><figcaption>SharedMailbox Creation Runbook</figcaption></figure><p>Script for full access :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/0*Vvvt1o-SyUwRNXcx" /><figcaption>Full Access Runbook</figcaption></figure><p>If you notice in shared mailbox runbook under the “Param” i have used the below code :</p><p>Param</p><p>(</p><p>[string] $DisplayName= “”,</p><p>[string] $Alias = “”,</p><p>[string] $Name= ‘“”</p><p>)</p><p>basically these are the parameter’s which are required to create the mailbox and these will be coming from our sharepoint list which is filled by the requestor . Similar pattern is followed for fullacess runbook.</p><p><strong>Microsoft Power Automate</strong></p><p>Now we create the Power Automate Workflow as per the steps mentioned in my diagram shown in beginning of this post.</p><ol><li>Sharepoint online will host the list where user can raise the request for shared mailbox creation and get them full access on the mailbox. Requestor has to provide the Display Name , Name &amp; alias for the shared mailbox which they want to be created ( as these are mandatory for shared mailbox to be created in exchange online). For simplicity i am assuming that requestor needs full access on the permission which he is getting created.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/0*3Nxvp0U4MBeOJ-rL" /><figcaption>Sharepoint List Format</figcaption></figure><p>2. When the request is submitted by requestor the power automate workflow is initiated , for the manager’s approval.</p><p>Note : Power Automate let’s you add ability to automatically lookup the manager as well from the Global Address list of O365 if updated and their will not be a requirement to get the filled manually .</p><p>Now let us look at our flow in Power Automate and i will further explain each part of the flow in detail in the next steps :</p><p>Go to Office.com — -&gt; Power Automate</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/369/1*RtFWsEAQHz_up6Dcks50JA.png" /><figcaption>Open Power Automate</figcaption></figure><p>In Power Automate : Create a new flow : Automated Cloud Flow</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/448/1*qF7QWbs3VC09PalvkVSJQg.png" /><figcaption>Create a Blank Flow</figcaption></figure><p>Name your flow and select the trigger for your new flow : ( Our flow is triggered when a new item in our sharepoint list is created)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/897/1*K-lCoknNd0XoUZTBpw07bg.png" /><figcaption>Naming the flow &amp; trigger selection</figcaption></figure><p>Complete flow will look like below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*F_AlL9ik9NzaVaqXGotOww.png" /><figcaption>Complete Flow</figcaption></figure><p>Now let’s dive into each section of the flow one by one</p><ol><li><strong>When a new item is created </strong>: Starting point of our flow is when a new item in our sharepoint list is created our flow is triggered :</li></ol><p>Enter the site address and list name for the SharePoint Online list that was created earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/569/1*wB_mtIIcg_sHesWRIUZvhg.png" /></figure><p>Once this is done , setup the manager’s approval part the flow as below :</p><p>2. <strong>Create an approval : </strong>Click on Next Step → Choose an operation → Approvals . We will set the <strong>Approval type</strong> to “Approve/Reject-Everyone must approve”. The <strong>Title</strong> can be whatever is appropriate for your workflow. Approval request will be sent to a requestor’s manager. The manager’s email email address is pulled from the SharePoint list by adding dynamic content to the field. For this scenario, the “<strong>Manager Email</strong>” value is used to populate the <strong>Assigned to</strong> field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/569/0*sek0MFyYZVD69cfA" /><figcaption>Approval Creation</figcaption></figure><p>3. Next , flow wait’s for approval in email</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/581/0*sZ03CFXFDL68HSv8" /></figure><p>4. After receiving the approval, we need to set the condition for approval and rejection scenarios . We are going to use the approval outcome in the condition setting. If the response is “Approve”, then that is a “yes” outcome. If not, then the outcome is “no”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ak1GWWCFpbt6zoyn" /></figure><p>Lets see what happens if Approval response is “<strong>Yes</strong>” and its actions :As per our workflow requirement if the Approval is “Yes” the flow should :</p><ol><li>Trigger an Azure automation job for shared mailbox creation and assign full access permission on that mailbox to requestor .</li><li>Send a confirmation mail to requestor on completion of both activities.</li></ol><p>If yes → Add an action — -&gt; Azure Automation — -&gt; Create a Job</p><p>Give a name to your Job tile and fill the appropriate field</p><p><strong>Subscription</strong> : select your azure subscription</p><p><strong>Resource Group</strong> : where your azure automation account is created</p><p><strong>Automation Account</strong> : select your azure automation account name</p><p><strong>runbook</strong> : Select the runbook which will perform this action</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/544/0*704g2SYQxS9KJYC7" /></figure><p>Runbook Parameter which we have defined in our runbook are to defined in our flow as well so that we can input their value from our sharepoint list. are defined in the advanced options:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/543/0*fjpclWY1yEJsn_61" /></figure><p>Add another Action for granting full Access :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/543/0*kT5hk64F-My45vCW" /></figure><p>Now we setup sending a mail confirmation to requestor on completion of request .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/554/0*9KqThrrqbDVwJrFa" /><figcaption>Send an email</figcaption></figure><p>Similarly In case approval response is “No” , we send a email to the requester regarding the same in the “No” section of the condition.</p><p>Now let us test our flow and see how things look from a user prospective :</p><p>You can test if your flow is working properly . Go to Power automate → Go to your flow — -&gt; Test</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/409/1*EZEdgZPtkVV5nUngLBGruQ.png" /></figure><p>Once we have clicked the <strong>Tes</strong>t button, we are presented with different options including:</p><p>Choose I’ll perform the trigger action and go to your sharepoint list and create a new item.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/292/0*_ZmyNNdjHhastNG9.png" /></figure><p>Once the item is created as below , the flow is triggered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/609/1*5IDOJmCOjrjxd7iaJHcZlw.png" /></figure><p>Once user has submitted a entry in the sharepoint list , approval flow starts :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/623/0*xX9FJ_WGQbc7z52D" /></figure><p>Mail for Approval is received in the manager’s inbox :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*V0bqzInbYNXZaD7-jTWAdw.png" /></figure><p>Now the flow looks like this :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/0*VluQlHpJk_8P72-q" /></figure><p>Once approved by manager , it moves to condition stage :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9b_PeJeZTlkBoz9w" /></figure><p>Below shows the status of the sharedmailbox runbook execution in azure automation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bt9exYR--3zXpM_o" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mIIeicfuy4e5qNhp" /></figure><p>Now the Flow status changes to this :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UOHUVYaZ4l01o1mA" /></figure><p>Now flow moves to executing the full access permissions by running the full access runbook :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gnQc9F-B_1Q4ioOQ" /></figure><p>Post this the flow is completed and confirmation is sent to the requestor</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AXqnT4jRrSSuWXbT" /></figure><p>and the requestor gets a confirmation in their inbox about mailbox creation.</p><p>To verify the creation of mailbox and access permissions we can log into the exchange control panel to see the mailbox :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oHyoE-Az-nDcQ6vh" /><figcaption>Shared Mailbox Created</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/0*1wueRuoyi267n6LF" /><figcaption>Full Access Granted</figcaption></figure><p><strong>Conclusion</strong></p><p>This is an example of how you as an IT professional can leverage the tools available in Office 365 to create custom apps and workflows for your Organisation, all without writing a single line of code.</p><p>Their are many advantages of automating such IT request in your environment . It reduces the time taken to cater to user request , automation allows users self service their request. No need to provide Service desk analyst or L1/L2 engineers access to admin access hence improving the security posture of your M365 subscription. This is one of many scenarios where we can use power automate and azure automation to make daily IT operations more efficient ,for e.g you can extend to include permissions for send-as permissions or create new flow’s to enable on-line archive for mailboxes, distribution list/ O365 group creation , run reports for exchange online , enable license and many more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad8e9382c25b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>