From collaborative apps in Microsoft Teams to Cloud PC—here’s what’s new in Microsoft 365 at Inspire

From collaborative apps in Microsoft Teams to Cloud PC—here’s what’s new in Microsoft 365 at Inspire

by | Jul 14, 2021 | Business, Microsoft 365, Technology

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

Announcing new hybrid-work innovations to the Microsoft cloud—the cloud built for a new world of work.

The post From collaborative apps in Microsoft Teams to Cloud PC—here’s what’s new in Microsoft 365 at Inspire appeared first on Microsoft 365 Blog.

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.

Create Private AKS Cluster using Bicep

Create Private AKS Cluster using Bicep

by | Jul 13, 2021 | Technology

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

Overview


This is a blog on how to use a modular approach for Infrastructure as Code (IaC) in provisioning a private AKS cluster and other related resources. The Bicep modules in the repository are designed keeping the AKS baseline architecture in mind. You can start using these modules as is or modify to suit your own needs.


Architecture


PrivateCluster.jpg


Setup


The Bicep modules will provision the following Azure Resources under subscription scope:



  1. A Resource Group with Baseline variables

  2. Hub VNet with required subnets

  3. Azure Firewall Subnet

  4. Azure Bastion Subnet

  5. A jumpbox subnet

  6. Spoke VNET with AKS cluster subnet and additional subnet for other services like Azure Container Registry etc.

  7. Azure Firewall and required routes

  8. Azure Bastion resource and a jumpbox VM without public IP for securing traffic

  9. Azure Container Registry for storing images.

  10. A Private Endpoint for ACR

  11. Private DNS Zone

  12. AAD Enabled, Managed Private AKS Cluster with monitoring Addon and Azure Policy enabled

  13. Private AK Cluster need the UDR routes enabled via Firewall.


Resource Provisioning


Clone the repo


git clone https://github.com/ssarwa/bicep

cd bicep

# You could use deploy.azcli as your working file. Don’t run the script as is!

Login to Azure


az login


az account set -s <Subscription ID>

Initialize variables


# Change the variables as required (baseline and location) on deploy.azcli

# Deploy the bicep script

az deployment sub create -n $baseline‘Dep’ -l $location -f main.bicep

The deployment could take somewhere around 20 to 30 mins. Once provisioning is completed you can use the cluster for your needs.


Next Steps



  1. Enable GitOps using Flux operator for Application deployment

  2. Enable IaC using CI/CD pipelines on Github Actions

Use guided integration to set up Fraud Protection for your business

Use guided integration to set up Fraud Protection for your business

by | Jul 12, 2021 | Dynamics 365, Microsoft 365, Technology

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

Adopting new systems can be a complex process that can lead to spending time and resources learning and setting up instead of focusing on your core business. When setting up a fraud protection system, you need to focus your resources on measuring the business impact and optimization rather than spending time doing setup tasks.

To simplify the Dynamics 365 Fraud Protection integration process, we have added a guided process experience.

The integration experience functionality, available as preview, provides a guided integration process for each product capability, with well-defined start and end points. We have included out-of-the-box snippets and step-by-step instructions that can be started from within the product. The guided processes are interactive and provide step-by-step integration instructions, including information about why something is required.

The integration processes have been grouped by the stages that you need to follow to set up a comprehensive fraud protection workflow.

Enable core integration

To integrate with Fraud Protection APIs, you must have an Azure Active Directory (Azure AD) application and set up device fingerprinting. Your Azure AD application is used to acquire access tokens, and device fingerprinting is used to get input for fraud assessments. These are the first steps needed to set up Fraud Protection. The integration wizard will walk you through this setup.

Integrate APIs

To benefit from the full suite of Fraud Protection functionality, next you will need to integrate your system with real-time APIs. Depending on your business scenarios, you may need to integrate with specific sets of APIs.

The real-time API integration experience has been split into two categories Purchase Protection and Account Protection based on the assessment types that are most pertinent to your business needs.

Each integration experience provides a milestone-based approach. When you successfully complete an API integration, you will be guided to the next integration phase so you will be able to track your progress.

Integration experiences can be launched more than once and can be personalized based on user input. For example, you may want to run the steps for integrating the Purchase API twice if you have two different online store fronts and want to integrate both.

Next steps

To learn more about integration experience capabilities, visit the Dynamics 365 Fraud Protection Portal or take a guided tour.

Join the Dynamics 365 Fraud Protection Insider Program to get an early view of upcoming features, to discuss integration best practices, and to learn how to combat fraud.

If you’re not currently using Dynamics 365 Fraud Protection, check out the free trial.

The post Use guided integration to set up Fraud Protection for your business appeared first on Microsoft Dynamics 365 Blog.

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.

Privacy Capabilities for Microsoft 365

by | Jul 12, 2021 | Technology

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

At Microsoft, we believe your data should be controlled by you. We are transparent about why we collect your data and how we use it across all of our products and services.


 


Organizations are generating and sharing more personal data than ever before as their employees fluidly transition between work and personal devices and networks. At the same time, the number of data breaches is increasing exponentially. There were over 800 data breaches in the first half of 2021 – 76% of 2020’s total breaches[1]. To protect consumer data from being compromised by increasingly sophisticated breaches, legislatures across the globe are introducing new privacy regulations. A recent study predicted that by 2023, 65% of the world’s population will have its personal information covered under modern privacy regulations, up from 10% today[2]. Most organizations still use spreadsheets, emails, and in-person communication for data mapping, and struggle to identify and effectively manage personal data in their environments.


 


Microsoft wants to help you on your privacy journey. Starting this week, organizations can use privacy capabilities for Microsoft 365 in preview. These capabilities help organizations gain visibility into the private data in their environment, proactively identify and protect against privacy risks, and manage subject rights requests (commonly known as ‘data subject requests’) at scale. Additionally, to meet organizations where they are in their privacy journey, we are enabling integration with our privacy capabilities to help customers deliver a unified response to subject rights requests.


 


Get Started


You can access the privacy capabilities for Microsoft 365 from the Microsoft compliance center.


 


Learn More


Read this document to learn more about privacy capabilities for Microsoft 365.


 


[1] First half 2021 Data Breach Analysis, ITRC


[2] New Privacy laws outside Europe and California: A global cheat sheet, Gartner

Experiencing Data Access Issue in Azure portal for Log Analytics – 07/11 – Resolved

by | Jul 11, 2021 | Technology

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

Final Update: Sunday, 11 July 2021 16:58 UTC

We’ve confirmed that all systems are back to normal with no customer impact as of 07/11, 15:45 UTC. Our logs show that the incident started on 07/11, 15:10 UTC and that during the 35 minutes that it took to resolve the issue some of the customers might have experienced data access issues and delayed or missed Log Search Alerts in Australia East region.
  • Root Cause: The failure was due to an issue in one of our backend services.
  • Incident Timeline: 35 minutes – 07/11, 15:10 UTC through 07/11, 15:45 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Saika
Initial Update: Sunday, 11 July 2021 16:07 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issues and delayed or missed Log Search Alerts in Australia east region.
  • Work Around: None
  • Next Update: Before 07/11 18:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Soumyajeet