Resource search results
11 - 20 of 227
Microsoft Azure Sphere Operating System currently supports two kinds of network connectivity: Ethernet and Wi-Fi. For customers that require connectivity to the Internet via cellular networks, one option is to use external hardware to route the Ethernet or Wi-Fi to the cellular network. This router-based architecture results in some implications that customers should be aware of. This paper discusses the cellular connectivity options immediately available for customers using Azure Sphere, addresses the security-critical functions that can only be performed through Azure Sphere OS-supported network connections, and identifies the limitations on security-related functions and guarantees that Azure Sphere offers when customers use a cellular-router-based system.
Learn how the new Azure Stack HCI service can help you with starting your hybrid journey with a hybrid and hyperconverged solution.
In Microsoft Azure, Azure Active Directory is the identity governance and administration layer that is used to manage access to resources such as instances of virtual machines, databases, applications, APIs, websites, etc. This identity layer is the control plane that helps protect your resources from intruders. In this paper, we describe the architectures and best practices for implementing identity and access management across separate Azure environments. Not all organizations need to run separate environments. This document will help you understand if this configuration is appropriate for your organization. We begin with an Introduction to delegated administration and isolated environments. In this introduction we describe various deployment scenarios and critical considerations for deciding if separate environments are appropriate for your organization. Ultimately, we help you choose the right architecture for your organization: Delegated administration in a single tenant, Resource isolation in multiple tenants, or Resource and identity isolation in multiple tenants. We then provide a comprehensive list of design considerations, or best practices.
Key considerations for running modern enterprise applications on PostgreSQL.
Cloud computing is empowering digital transformation across industries. Silicon is the foundation of the technology industry, and new opportunities are emerging in cloud computing for silicon (semiconductor) development. The workflows for silicon development have pushed the limits of compute, storage, and networking. Over time, these workflows have expanded to handle the increasing size, density, and manufacturing complexity of the industry. This has pushed the limits of high-performance computing (HPC) and storage infrastructure. Azure provides a globally available HPC platform that’s reliable and scalable. It offers an array of security tools and capabilities, and it meets current and emerging infrastructure needs with a silicon design and development workflow based on EDA software. Read this white paper to learn more about configuring Azure services for silicon development.
This paper offers a brief overview of United States, United Kingdom and European Union export control laws and regulations as they may apply to use of Microsoft Azure cloud services and platform, with some general guidance concerning the considerations that Azure customers should bear in mind to assess their obligations under U.S., UK, and EU export controls. The Azure platform offers flexible options, capabilities and tools that customers may use to help ensure export-compliance in their use of Azure cloud services.
This document explains the following aspects of Azure Active Directory: • Azure AD Components: What are the different components of Azure AD. This will help you to understand the later sections of the document. • Core Data and Location: What customer data is used by Azure AD and where is it located. • Data Protection: How is the directory data protected at transit and at rest. • Data Flow: How data from various sources such as on premises directories and applications flows to and from Azure AD. • Data and Operations: What data and operational procedures are used by the Azure AD engineering team to manage the service. The target audience of this document is enterprise security evaluators, identity, and access management (IAM) architects, policy makers and regulators, as well as customers with compliance requirements or regulated environments.
This document is intended for Azure customers who are considering deploying applications subject to SOX compliance obligations. It provides customer guidance based on existing Azure audit reports, as well as lessons learned from migrating internal Microsoft SOX relevant applications to Azure.
The goal of this GxP guidelines document is to provide life sciences organizations with a comprehensive toolset for using Microsoft Azure while adhering to industry best practices and applicable regulations. It identifies the shared responsibilities between Microsoft and its life sciences customers for meeting regulatory requirements, such as FDA 21 CFR Part 11 Electronic Records, Electronic Signatures (21 CFR Part 11), and EudraLex Volume 4 – Annex 11 Computerised Systems (Annex 11).
Deploying Microsoft Azure solutions can give educational organizations a method of focusing on their core business—education—while maintaining cost-effective IT services in a more secure FERPA-compliant environment. However, it is important for educational organizations to understand their unique threat environment so that they can see what they need to deploy onsite and how it meshes with what Microsoft Azure provides in the cloud. Using the shared responsibility strategy, Microsoft can help assure the protection of student data and FERPA compliance. This paper will be most helpful to those in educational organizations who need guidance and best practices in designing secure solutions on Azure.