This GA release brings forward a few significant changes:
We have split the Storage SDKs into four packages, one each for Blob, Table, Queue, and File. As announced, this was done in order to reduce the footprint of the libraries and allow developers to consume only the packages they are interested in. Support is now available for newer Azure Storage REST API versions and service features. See below for details on each SDK. Azure Storage SDK for Python
Storage SDK packages for Blob, File, and Queue in Python are available on PyPi with version 1.0. This release supports the April 4, 2017 REST API version, bringing support for archival storage and blob tiering. Table package is released under the name Azure-Cosmosdb-table.
Here is a Hello World sample with the Storage SDK for Python:
from azure.storage.blob import BlockBlobService import os # Create a blob service client block_blob_service = BlockBlobService(os.environ.get(‘AZURE_STORAGE_ACCOUNT_NAME’), os.environ.get(‘AZURE_STORAGE_ACCOUNT_KEY’)) # upload a blob from text block_blob_service.create_blob_from_text( ‘mycontainer’, ‘myblockblob’, ‘Hello World!’ ) # download a blob into a buffer blob
Modern applications are taking maximum advantage of the agility and flexibility of the cloud by moving away from monolithic architectures and instead using a set of distinct services, all working together. This includes foundational services offered by a cloud platform like Azure (Database, Storage, IoT, Compute, Serverless Functions, etc.) and application-specific services (inventory management, payment services, manufacturing processes, mobile experiences, etc.). In these new architectures, event-driven execution has become a foundational cornerstone. It replaces cumbersome polling for communication between services with a simple mechanism. These events could include IoT device signals, cloud provisioning notifications, storage blob events, or even custom scenarios such as new employees being added to HR systems. Reacting to such events efficiently and reliably is critical in these new app paradigms.
Today, I am excited to announce the general availability of Azure Event Grid, a fully managed event routing service that simplifies the development of event-based applications.
Azure Event Grid is the first of its kind, enabling applications and services to subscribe to all the events they need to handle whether they come from Azure services or from other parts of the same application. These events are delivered through push semantics, simplifying your code and reducing your
https://powerbi.microsoft.com/en-us/blog/2-1-webinar-sharepoint-loves-powerapps-a-summary-of-sharepoint-powerapps-features-by-ashish-trivedi/Source: https://powerbi.microsoft.com/en-us/blog/2-1-webinar-sharepoint-loves-powerapps-a-summary-of-sharepoint-powerapps-features-by-ashish-trivedi/ In this session, we will summarise the SharePoint features which are being made available in PowerApps. This include, built in support for different field types, new/edit/display forms, built in connectors or rules, connecting READ MORE
Last week in Azure, several announcements were made for Zone Redundant capabilities now in public preview that build on Azure Availability Zones. In addition, new backup and update capabilities make it easier to manage and help protect your virtual machines. There’s also a new, intuitive and simplified onboarding experience for Azure Site Recovery service for VMware to Azure.
Now in preview
Zone Redundant Virtual Machine Scale Sets now available in public preview – Zone Redundant Virtual Machine Scale Sets bring the scalability and ease of use of scale sets to availability zones by automatically spreading your virtual machines across availability zones. You don’t need to worry about distributing VMs across zones, choosing which VMs to remove when scaling in, etc.
Azure Zone Redundant Storage in public preview – Zone Redundant Storage (ZRS) greatly simplifies development of highly available applications by storing three replicas of your data in different Availability Zones, with inserts and updates to data being performed synchronously across these Availability Zones. This enables you to continue to read and write data even if the data in one of the Availability Zones is unavailable or unrecoverable. ZRS is built over Availability Zones in Azure which provide resilience against failures
An increasing number of developers across the globe use GitHub to host their projects, and many of them use GitHub public repositories for their open source work. While this is a great way to contribute and leverage the power of the community, it does come with a unique set of responsibilities. Particularly around managing credentials and other secrets.
Examples of Azure secrets are authentication credentials that should not be made public. These include things such as passwords, private keys, database connection strings, and storage account keys that are managed by Azure tenants.
In Azure, we take security very seriously. Azure secrets are considered sensitive and should not be made publicly available. An exposed secret could lead to the compromise of your Azure subscription, your cloud assets, as well as on-premises assets and data; putting your applications or services at significant risk.
Microsoft Credential Scanner Preview
To help protect our customers, Azure runs Credential Scanner aka CredScan. CredScan monitors all incoming commits on GitHub and checks for specific Azure tenant secrets such as Azure subscription management certificates and Azure SQL connection strings.
Internally at Microsoft we’ve been developing and leveraging CredScan to protect Azure and our 1st party services and
Azure Network Watcher Connection Troubleshoot, previously in preview as Connectivity Check, is making general availability sporting a new name. Connection Troubleshoot, part of our Network Watcher suite of networking tools and capabilities, enable you to troubleshoot network performance and connectivity issues in Azure.
Continuing the expansion of tools within Azure Network Watcher, this new addition provides visualization of the hop by hop path from source to destination, identifying issues that can potentially impact your network performance and connectivity.
Network Watcher Connection Troubleshoot features
With the addition of Connection Troubleshoot, Network Watcher will see an incremental increase in its capabilities and ways for you to utilize it in your day to day operations. You can now:
Check connectivity between source (VM) and destination (VM, URI, FQDN, IP Address) Identify configuration issues that are impacting reachability Provide all possible hop by hop paths from the source to destination Hop by hop latency Latency – min, max, and average between source and destination A topology (graphical) view from your source to destination Number of packets dropped during the connection troubleshoot check
Connectivity troubleshoot check graph view output Source: Azure VM and Destination: www.bing.com.
What kind of issues can Connection Troubleshoot detect?
The MySQL sys schema, which is fully enabled in Azure Database for MySQL 5.7, provides a powerful collection of user friendly views in a read-only database. Building on the MySQL Performance and Information Schemas, you can use the MySQL sys schema to troubleshoot performance issues and manage resources efficiently.
The MySQL Performance Schema, first available in MySQL 5.5, provides instrumentation for many vital server resources such as memory allocation, stored programs, metadata locking, etc. However, the Performance Schema contains more than 80 tables, and getting the necessary information often requires joining tables within the Performance Schema, as well as tables from the Information Schema. Let’s look more closely at how to use the MySQL sys schema.
There are 52 views in the sys schema, and each view is prefixed by one of the following:
Host_summary or IO: I/O related latencies. Innodb: Innodb buffer status and locks. Memory:Memory usage by the host and users. Schema: Schema related information, such as auto increment, indexes, etc. Statement: Information on SQL statements; this can be statements that resulted in a full table scan or long query time. User: Resources consumed and grouped by users. Examples are file I/Os, connections, and memory. Wait: Wait
Azure Database for MySQL is a PaaS (Platform as a Service) solution that Microsoft offers on Azure. Using Azure managed services for MySQL (and PostgreSQL), enables one to easily build an intelligent and secure application.
Though Microsoft has done a lot of work to optimize database performance, sometimes a simple query can easily become a bottle neck impacting overall database performance. Luckily, MySQL integrates a handy tool – the EXPLAIN statement – that can profile client queries and thus help you identify the root cause of a slow query. You can use an EXPLAIN statement to get information about how SQL statements are executed. With this information, you can profile which queries are running slow and why.
The output below shows an example of the execution of an EXPLAIN statement.
mysql> EXPLAIN SELECT * FROM tb1 WHERE id=100G *************************** 1. row *************************** id: 1 select_type: SIMPLE table: tb1 partitions: NULL type: ALL possible_keys: NULL key: NULL key_len: NULL ref: NULL rows: 995789 filtered: 10.00 Extra: Using where
As you can see from this example, the value of key is NULL. This means that MySQL cannot find any indexes optimized for the query and it performs a full table
Azure ExpressRoute allows enterprise customers to privately and directly connect to Microsoft’s cloud services, providing a more predictable networking experience than traditional internet connections. ExpressRoute is available in 42 peering locations globally and is supported by a large ecosystem of more than 100 connectivity providers. Leading customers use ExpressRoute to connect their on-premises networks to Azure, as a vital part of managing and running their mission critical applications and services.
Cisco to build Azure ExpressRoute practice
As we continue to grow the ExpressRoute experience in Azure, we’ve found our enterprise customers benefit from understanding networking issues that occur in their internal networks with hybrid architectures. These issues can impact their mission-critical workloads running in the cloud.
To help address on-premises issues, which often require deep technical networking expertise, we continue to partner closely with Cisco to provide a better customer networking experience. Working together, we can solve the most challenging networking issues encountered by enterprise customers using Azure ExpressRoute.
Today, Cisco announced an extended partnership with Microsoft to build a new network practice providing Cisco Solution Support for Azure ExpressRoute. We are fully committed to working with Cisco and other partners with deep networking experience to build and expand on
https://powerbi.microsoft.com/en-us/blog/share-reports-with-your-teams-and-partners/Source: https://powerbi.microsoft.com/en-us/blog/share-reports-with-your-teams-and-partners/ We’re excited to announce we’re rolling out report sharing to users worldwide. Now reports and dashboards have the same sharing features, making it even easier for Power BI users to collaborate with their READ MORE