Introduction: Email can fill your Outlook Inbox quickly – new messages, replies, and forwards. Before you know it, you could have thousands of messages. Keep your Outlook inbox and its folders under control by moving older items you want to keep to an archive. Email archiving helps in saving and preserving data contained in email messages so it can be searched and accessed later. An archive mailbox is a specialized mailbox that appears alongside the users’ primary mailbox folders in Outlook or Outlook Web App. Users can access the archive in the same way that they access their primary mailboxes. Enabling In-Place Archive: For moving the mailbox items to Archive, firstly we need to enable In-place archive for that mailbox. Go to Exchange Admin Center > Recipients > Mailboxes. Select user for whom you want to enable In-place archive. You will be getting the option to enable archiving as shown in below image. After In-place archive is enabled, in the mailbox type you can see Archive in brackets (as shown in below image). Within 15 minutes, user will be able to see In-place archive folder in their mailbox which is a secondary mailbox and can be accessed as primary mailbox is accessed. Creating Retention Tag and Retention Policy: Retention Tag – Retention tags define and apply retention settings to messages and folders in a user’s mailbox. Retention tags specify how long a message is kept and the action taken when the message reaches the specified retention age. After enabling In-Place Archive, we need to move the items to archive. We can move the items by – 1. Moving the mailbox items manually. 2. Move messages using Inbox rules. 3. Move messages using retention policies. Here, we will see how to create retention tag and policy so that the mailbox items will be moved to Archive. Go to Exchange Admin Center > Compliance Management. To create a Retention Policy, firstly we need to create Retention tag and then attach that tag with a policy which is called retention policy. You will be getting 3 options to create a Retention tag – a. Default policy tag which will be applied to entire mailbox. Note – DPT will be applied to all items in the mailbox that don’t have a retention tag already applied to it. b. Retention policy tags which will be applied to a default folder, such as Inbox (Does not support Archive action). c. Personal tags which can be applied by users to items and folders. Select default policy tag. Provide a name to tag and choose the retention action which will be taken after the items reaches retention age which also needs to be mentioned in no. of days (see below image). In this case I have created a retention tag so that when the items will reach 90 days it will be moved to archive. After creating Retention tag, we need to create retention policy, provide a name to the policy and add the retention tag. After the Retention Policy is created, it needs to be assigned to the users. For the same, go to Recipients > Mailboxes. Select User and click on edit. Go to Mailbox features and apply  Retention Policy to user. It may take some time for the retention tag to appear in the mail settings > retention policies (see below image). After the Retention Policy is applied to the mailbox, the items which has reached their retention age of 90 days will start moving to In-place Archive. Note – It can take up to 7 days for the items to be moved in to In-Place Archive depending upon the number of items. Conclusion: In this way we can create Retention tag and policy for Email Archiving which will keep Outlook inbox and its folders managed by moving the older items to archive.

Introduction: Data loss prevention (DLP) is a strategy for making sure that end users do not send sensitive information outside the corporate network. You can set up policies to help make sure information in email and docs isn’t shared with the wrong people. With a DLP policy, you can identify, track, and protect sensitive information across Office 365. Create a DLP Policy in Office 365 Security & Compliance center: Go to Office 365 Admin Center > Security & Compliance > Data Loss Prevention. You can choose to create a policy from a template or create a custom policy. In the next step, you need to name your policy. The next step is to choose location, whether it should be for all locations or for specific. If you select, Let me choose specific location you will getting option in below image. Under policy settings, you can choose base setting (Find content that contains) or you can Use advanced settings. If you choose advanced settings then you can customize a New Rule. By clicking New Rule, you will get options to create a rule. Provide the conditions and actions. In conditions you can add sensitive information types which is available or you can select Label which has been applied to the document for data classifcation.Labels need to be created and published first in order to use it in a DLP Policy. You can create Labels from Office 365 Security & Compliance. Labels can be applied to the documents in OneDrive and SharePoint Online. You can also configure other settings like User Notification, User overrides and incident reports. After creating a Rule, Save the changes. In the Conditions option you can see the Label (see below image) which has been applied to the DLP rule “Cloud Sensitive Information”, which has been published first and then applied to the document. In the below image, showing Label which has been applied to the Cloud DLP Policy. After creating the policy, it may take upto 24hrs for the changes to take effect. Testing DLP Policy: After creating policy, if user will try to share the document with external users he will be getting policy tips (as shown in below image). Also, if you try to send the sensitive information of your organization on an email outside your organization, policy tips will be shown (see below image). If the user will override the policy tip, then he has to enter a business justification or report it as a false positive. Conclusion: This is how you can create DLP Policies and prevent your organisations classified data from leaking.

Introduction: Azure Machine Learning Studio is an amazing tool that lets us create efficient ML experiments with simple drag and drop features. We can predict anything from Flight Predictions to Churn Analysis. But what if we want to represent this predicted data a more visually appealing format? Well it is possible to do this by representing your predictions on Power BI! Pre-Requisites: Basic Understanding of Azure Machine Learning Studio. Basic Understanding of Power BI. A Blob Container created on Azure Storage.   Steps: Create your Azure Machine Learning Experiment on Azure Machine Learning Studio. Convert your Training Experiment to a Predictive Experiment and Deploy it as a Web Service. We will create a Console application in Visual Studio and copy paste the code inside Batch Execution. For automation we can create automated data pipelines but for now we will just use a simple Console application. Remove the existing code from the Console Application and copy paste the Batch Execution code. Install the necessary Nuget Packages and also update the following parameters. – BaseURL will be the same. – Storage Account Name, Storage Account Key and Storage Container Name will be parameters that can be found in your Azure Blob Storage which was created. – Api Key can be found in the Web Experiment Page in Azure Machine Learning Studio. – The input path is the path where you have saved your input csvfile for Batch Execution. Your Input csv file should have all the features which you have used to train your experiment After you run your Console application a new output1results.csv file should get generated in your Blob Container. The output results should include the labels which your experiment generates in it’s output. It should include the Scored Labels and Scored Probabilities labels as well. Now you can get your data using Azure Blob Storage as your source in Power BI and use the columns in the output1result.csv file to generate your ML Predicted Reports. The Report can look something like this. I hope this blog helps you to combine Azure Machine Learning Studio and Power BI to create a powerful predictive solution.

Background: When an enterprise transitions to Cloud, it may still need to leave some assets on-premises for technical or security reasons. Typically SQL DBs will be On-premises for most enterprises. But this should not stop the enterprise from having their Web apps, APIs, services and mobile apps on cloud. The major hindrance in this scenario will be the feasibility for connecting the Cloud based services to On-Prem SQL for seamless transition. Azure allows you to create layer on top of this On-prem assets while safely connecting to them back on your premises using Hybrid Connections. Supported assets include MS SQL Server, MySQL or any resource that runs on static TCP Port. Prerequisites: Visual Studio 2013 or later SQL Server 2008/ 2012 with SQL server authentication Azure SDK Microsoft Azure Subscription Steps: Create SQL Server DB and table. Cerate an SQL User to connect which will be used in the .NET application. Also create some sample data in the table. Create a .NET web application which will read data from table create in Step 1. The connection string will look something like below. Host the application on Local IIS and ensure it works and can connect to SQL. Now host the application on Azure as web-app. You can refer the below link for steps to create Azure Web app. https://github.com/Microsoft/HealthClinic.biz/wiki/Create-and-deploy-an-ASP.NET-web-app-in-Azure-App-Service You will notice that the application will throw error because it will not be able to connect to the On-prem SQL. We will now create a Hybrid connection to the SQL DB. Navigate to App Service which we created in Step 4 in Azure, and navigate to Networking. Click on Hybrid Connections > Configure your Hybrid Endpoints Create New Hybrid Connection. Enter the details for Hybrid connection like below: Note: usually the TCP Port no for SQL is 1433. Please check for the SQL you are configuring. Download the Hybrid connection manager and install on the SQL server or any server on the same network. Open the installed Hybrid Connection Manager UI, and enter the connection string of the Hybrid connection we created in Azure. You can get the connection string of the Hybrid connection by clicking on it like below. Enter the Connection String in Hybrid Connection Manager UI. If everything is proper, you should see the status as Connected Like below in the tool as well as in Azure. In Azure: Other Notes: If you are facing issues with connection, you can restart the Hybrid Connection service from Local services. Please comment below in case of queries.

Introduction: It is important that you have your organization hierarchy setup in order to use advance features. To setup Manager for User in Office 365, there’s a couple of ways how you can make that happen. Manager setup in Exchange Online. Manager setup in Azure AD. Manager setup in Exchange Online: 1. You need to login as administrator to your Office 365 and then choose ‘Admin Centers’, and ‘Exchange’. 2. Then go to ‘Recipients’ left menu item, search for the person that you want to manage, highlight the person and choose details. 3. Navigate down to Organization and then browse their manager. Manager Setup in Azure AD: Alternative is to set user’s manager in Azure Active Directory directly. To do that, you need to login as administrator to your Azure portal, Users and Group > All User. In order to set Manager in Azure AD, You will need to know manager’s person object ID to set it as a Manager ID for user (which you can look up by checking manager’s profile)’ Manager’s Profile – User’s Profile – After filling Manager ID and saving user profile, Manager will also be shown after few minutes in Mailboxes (Exchange Online). Manager setup can also be done in Dynamics 365, for doing so login to Dynamics 365. And, go to Settings > Users > Organization information and search for Manager of that user. Conclusion: In this way you can setup hierarchy in your Organization which is important in order to use full and advance features, you can also setup manager form Dynamics 365. Setting Manager information between Exchange Online and Azure AD will be synced.

Introduction: Many of the organizations are using  SharePoint Online in Office 365 as their content management system and it is essential to protect data so that the sensitive data does not slip into false hands. It is here we can use Multi-Factor Authentication and we can do this through Azure AD for that tenant by creating a Dynamics group for ‘External users’ and then create a conditional access policy and apply it to SharePoint Online. Creating a Group for External Users: Login to Azure AD Portal, and go to Azure AD > Users and Groups > All Groups and click New Group. Provide a name and description to this group and  select membership type (Dynamic User). Click Add query -> Create to make the group dynamic. It will take some time for the group to populate. After Group is created, you need to provide Conditional access to this Group. Create a Conditional Access Policy for SharePoint Online: Login to Azure AD Portal, go to Enterprise Application > Conditional Access and click on New Policy. Provide the name to the policy. Under Assignment > Users and Groups, select Include > Select Users and groups > Select, and then chose the group whom you want to provide the policy (External users). Under Assignment, go to Cloud Apps >Include > Select, and then choose the application (Office 365 SharePoint Application). Under Condition, select Condition if you want. Under Access Control, go to Grant and select Grant access and then choose Require multi-factor authentication. At last, toggle the Enable policy switch to ON and click Create. To verify if the policy is created, navigate to Conditional Access and check the policy name and if it is enabled. Wait for few minutes for the policy to take effect, after that you can check by sharing a document from SharePoint to external user. It will ask for authentication (see below image). Conclusion: In this way, you can create a conditional access policy and protect the sensitive data in your SharePoint Online. Hope this will be useful.

Introduction: You can use alert features in Office 365 to view and manage alerts for your Office 365 organization, including managing advanced alerts as part of Advanced Security Management. Advanced Security Management is available with Office 365 Enterprise E5, if your organization is using another Office 365 subscription, Advanced Security Management can be purchased as an add-on. After purchasing this add-on, you will be able to see Manages Advance Alerts under Alerts in office 365 security and compliance. In Office 365 Security & Compliance, go to Alerts > Manage advance alerts. Choose Go to Advance Security Management.In Advance Security Management portal, you can: Define policies and set up alerts and actions. Know about cloud usage across your organization through reports. Manage third party apps that people in your organization are using with Office 365. Create a new activity policy: From the Control menu of Advance Security management portal, select Policies. Click Create policy, and then select Activity policy. On the Create activity policypage, type the Policy name and Description. You can base a new policy on one of the default templates, if you like, by choosing one in the Policy template drop-down menu. Choose a policy severity and category for this policy. This can help you filter and sort alerts that have been triggered. Choose Activity filtersto set up other actions that will trigger an alert based on this policy. Check Create alert to receive notifications from this policy. Choose Actionsthat should be taken when an alert is triggered to suspend the user or require the user to sign in again to Office 365. When an activity matches a policy, alerts will be generate and notification will be sent to the mail ID enabled for getting alerts (see below screen shot) Email will be coming from this mail id. You can also receive SMS, for the same you must provide contact number. After you got the email notification, you can also view the details and take necessary actions on alert in Portal. You will able to see all the alerts under Alert By clicking on Alert which you got, you can see the details, activity log and take necessary actions on the alert. Conclusion: It is a good practice to set advance alerts which helps in monitoring the user activities by getting alert notifications.  

Introduction: Missing Registration For Location Error Can come when we are trying to publish the web application on azure from Visual studio. Solution: There are many blogs which says updating your  visual studio or Upgrading Azure SDK will resolve your problem but this solutions did not work for me. So I used alternative approach for publishing. Steps: Publish your web application using visual studio. It gives this  error. but It creates App Service Plan and App Service in Azure.  sign in to portal.azure.com Select the App Service which you have created. Click on Get Publish Profile. Now Again Go to Visual studio and Publish. This time while publishing select Import. Select the file which you have downloaded from azure. Click Ok. Click On Publish. 10. Your Application will get Publish. I hope this solve your issue also.

Introduction: When content reaches the end of its retention period, there are many reasons that you might want to review that content. You might need to assign a different retention period, suspend the deletion, etc. A disposition review includes only content in SharePoint sites, OneDrive accounts, and sites for Office 365 groups. A disposition review can’t include content in Exchange Online, Skype, public folders, or mailboxes for Office 365 groups. Sign in with Office 365 credentials, go to Admin Center > Security & Compliance > Data Governance > Disposition. Permission for Disposition: Reviewers must be the member of Disposition Management role and the View-only Audit Logs role. Setting up the Disposition review by creating a Label: Disposition review option is only available when you create a Label with retention settings. This option is not available in a retention policy. For creating a Label, navigate to Office 365 Security & Compliance, go to Classification > Labels. With Labels, you can classify data across your organization for governance, and enforce retention rules based on that classification. Switch toggle button to ON for applying Retention. Tick Trigger a Disposition review for setting up Disposition. When a content (to which this label is applied) reached retention period, reviewer is notified by email that content is ready to review. Reviewer can then go to Disposition page and select one or more item. The reviewer can: Apply a different Label. Extend the retention period. Permanently delete the item Export the Disposition item: In addition, you can export the items in .csv file that you can open in excel. Conclusion: It is important to review content when it reaches it’s retention period so if it requires you can assign different retention tag or label.

Introduction: Supervision lets you define policies that capture email and 3rd-party communications in your organization so they can be examined by internal or external reviewers. For creating Supervision policy, one must made add himself to the Supervision review role group so that they can set up policies. Go to Office 365 admin center > Security & Compliance > Permissions. Or Sign in to https://protection.office.com with your Office 365 credentials. Create Policy for Supervision: Go to Office 365 Security & Compliance > Data governance > Supervision. Click Create and then follow the wizard to set up the following pages of the policy. Enter a name and description for your policy. Choose users to supervise, here you can provide list of users or you can make Group in Office 365 and provide the Group name. If you provide Group, then you can exclude any user from Supervision by providing that user name under Exclude these users. Choose communications to review. If you want to scope the review further, click Add a condition. You can specify multiple conditions. Specify percentage to review. If you want to reduce the amount of content to review, specify a percentage. If you want reviewers to review all items, enter 100%. The users and groups you choose will use the Supervision app in Outlook web app to examine the communications that are returned by this policy. You can include email addresses for internal and external reviewers. After you have completed all sections of Supervision policy, review your settings and click Finish. Reviewers will use the Supervision add-in for Outlook web app to review communications. The add-in is installed automatically in Outlook web app for all reviewers you specified in the policy. Conclusion: It is good practice to create Supervision policy to capture email communication in your organization.