Category: Microsoft
Category Archives: Microsoft
It’s Nearly 2025 and Meeting Channel invites still don’t work properly
With channel meetings, all members get a meeting invite regardless of whether the organizer invites them or not.
Why even offer the ability to invite individuals in the first place?
It’s been so long, I’m starting to think this was by design and MS has no intention of fixing it.
With channel meetings, all members get a meeting invite regardless of whether the organizer invites them or not. Why even offer the ability to invite individuals in the first place? It’s been so long, I’m starting to think this was by design and MS has no intention of fixing it. Read More
Hidden Symbol in Word; Cannot Find and Replace
When copying pasting from web pages or from Google email, I often encounter this weird symbol, imbedded in the document and only visible from the Show/Hide function. It creates an extra space in documents. Problem is, I cannot do a “Find/Replace” to remove it from Word docs. Can someone tell me what this character is referred to in Word and how to “Find/Replace” it? Thanks.
When copying pasting from web pages or from Google email, I often encounter this weird symbol, imbedded in the document and only visible from the Show/Hide function. It creates an extra space in documents. Problem is, I cannot do a “Find/Replace” to remove it from Word docs. Can someone tell me what this character is referred to in Word and how to “Find/Replace” it? Thanks.Hidden Symbol? Read More
Update a sharepoint Excel file with the contents of multiple Excels in another folder
For context we recieve a monthly Excel report every month that is automatically upload to our Sharepoint.
At the moment we have someone manually copy and paste the content from these newly uploaded files into a “master worksheet” that contains all the reports data in a single file. I want to know if there is a way that we that we can automate the process of updating this excl file?
The tabs and columns on all the Excel’s are exactly the same.
For context we recieve a monthly Excel report every month that is automatically upload to our Sharepoint. At the moment we have someone manually copy and paste the content from these newly uploaded files into a “master worksheet” that contains all the reports data in a single file. I want to know if there is a way that we that we can automate the process of updating this excl file? The tabs and columns on all the Excel’s are exactly the same. Read More
Re: Notes
How do I recover notes that were on my IPhone previous to today? I deleted my account to register it again today and my notes were gone when I added my email back to my phone
How do I recover notes that were on my IPhone previous to today? I deleted my account to register it again today and my notes were gone when I added my email back to my phone Read More
Update: Cost-effective genomics analysis with Sentieon on Azure
This Blog was Co-Authored by Don Freed – Sr. Bioinformatics Scientist, Brendan Gallagher – Head of Business Development at Sentieon, Inc.
In our previous blog, we discussed benchmarking the performance of Sentieon’s, DNAseq and DNAscope pipelines using Azure instances using v202112.05 of the software. Since the publication of those results, there have been significant updates to the Sentieon software. As a result, we have updated the benchmarking to use Sentieon version 202308.01. We break down the runtime and cost of the pipelines on a wide range of currently available instances. These benchmarks use publicly available datasets, and the pipeline is available on Github.
Additionally, we have worked with Sentieon to develop a Terraform template for deploym
ent of the license server.
Running Sentieon on Azure
The pipelines and scripts needed for setup used in this benchmarking are provided on GitHub.
Instance Setup
The script at misc/instance_setup.sh performs initial setup of the instance and download/installation of software packages used in the benchmark.
Input datasets
In these benchmarks, as we stated before, we use the GIAB HG002 sample sequenced on multiple sequencing platforms. Input datasets for the benchmark are recorded in the config/config.yaml. With the exception of the Element dataset, that you will have to download on your own.
We recommend downloading all the files and placing them in an azure blob storage. You can use AzCopy to transfer the required files to your own Storage account using a shared access signature with “Write” access. Then we recommend updating the configs to use a shared access signature to each file. The pipeline will automatically download input files.
Input FASTQ were obtained as previously outlined, we have added the new ONT dataset below:
ONT HPRC
https://human-pangenomics.s3.amazonaws.com/submissions/0CB931D5-AE0C-4187-8BD8-B3A9C9BFDADE–UCSC_HG002_R1041_Duplex_Dorado/Dorado_v0.1.1/stereo_duplex/11_15_22_R1041_Duplex_HG002_1_Dorado_v0.1.1_400bps_sup_stereo_duplex_pass.fastq.gz
https://human-pangenomics.s3.amazonaws.com/submissions/0CB931D5-AE0C-4187-8BD8-B3A9C9BFDADE–UCSC_HG002_R1041_Duplex_Dorado/Dorado_v0.1.1/stereo_duplex/11_15_22_R1041_Duplex_HG002_2_Dorado_v0.1.1_400bps_sup_stereo_duplex_pass.fastq.gz
https://human-pangenomics.s3.amazonaws.com/submissions/0CB931D5-AE0C-4187-8BD8-B3A9C9BFDADE–UCSC_HG002_R1041_Duplex_Dorado/Dorado_v0.1.1/stereo_duplex/11_15_22_R1041_Duplex_HG002_3_Dorado_v0.1.1_400bps_sup_stereo_duplex_pass.fastq.gz
https://human-pangenomics.s3.amazonaws.com/submissions/0CB931D5-AE0C-4187-8BD8-B3A9C9BFDADE–UCSC_HG002_R1041_Duplex_Dorado/Dorado_v0.1.1/stereo_duplex/11_15_22_R1041_Duplex_HG002_4_Dorado_v0.1.1_400bps_sup_stereo_duplex_pass.fastq.gz
https://human-pangenomics.s3.amazonaws.com/submissions/0CB931D5-AE0C-4187-8BD8-B3A9C9BFDADE–UCSC_HG002_R1041_Duplex_Dorado/Dorado_v0.1.1/stereo_duplex/11_15_22_R1041_Duplex_HG002_5_Dorado_v0.1.1_400bps_sup_stereo_duplex_pass.fastq.gz
https://human-pangenomics.s3.amazonaws.com/submissions/0CB931D5-AE0C-4187-8BD8-B3A9C9BFDADE–UCSC_HG002_R1041_Duplex_Dorado/Dorado_v0.1.1/stereo_duplex/11_15_22_R1041_Duplex_HG002_6_Dorado_v0.1.1_400bps_sup_stereo_duplex_pass.fastq.gz
https://human-pangenomics.s3.amazonaws.com/submissions/0CB931D5-AE0C-4187-8BD8-B3A9C9BFDADE–UCSC_HG002_R1041_Duplex_Dorado/Dorado_v0.1.1/stereo_duplex/11_15_22_R1041_Duplex_HG002_7_Dorado_v0.1.1_400bps_sup_stereo_duplex_pass.fastq.gz
https://human-pangenomics.s3.amazonaws.com/submissions/0CB931D5-AE0C-4187-8BD8-B3A9C9BFDADE–UCSC_HG002_R1041_Duplex_Dorado/Dorado_v0.1.1/stereo_duplex/11_15_22_R1041_Duplex_HG002_8_Dorado_v0.1.1_400bps_sup_stereo_duplex_pass.fastq.gz
https://human-pangenomics.s3.amazonaws.com/submissions/0CB931D5-AE0C-4187-8BD8-B3A9C9BFDADE–UCSC_HG002_R1041_Duplex_Dorado/Dorado_v0.1.1/stereo_duplex/11_15_22_R1041_Duplex_HG002_9_Dorado_v0.1.1_400bps_sup_stereo_duplex_pass.fastq.gz
https://human-pangenomics.s3.amazonaws.com/submissions/0CB931D5-AE0C-4187-8BD8-B3A9C9BFDADE–UCSC_HG002_R1041_Duplex_Dorado/Dorado_v0.1.1/stereo_duplex/11_15_22_R1041_Duplex_HG002_10_Dordo_v0.1.1_400bps_sup_stereo_duplex_pass.fastq.gz
https://human-pangenomics.s3.amazonaws.com/submissions/0CB931D5-AE0C-4187-8BD8-B3A9C9BFDADE–UCSC_HG002_R1041_Duplex_Dorado/Dorado_v0.1.1/stereo_duplex/11_15_22_R1041_Duplex_HG002_11_Dorado_v0.1.1_400bps_sup_stereo_duplex_pass.fastq.gz
The input files vary in their coverage, so the datasets with FASTQ input were down-sampled to approximately 93 billion bases (~30x coverage) prior to processing with the Sentieon secondary analysis pipelines. The Ultima CRAM file was not down-sampled and is at 40x coverage as recommended by Ultima Genomics. The ONT duplex sample was not down-sampled and is at approximately 30x coverage.
The data were processed using the hg38 reference genome. The reference genome at https://giab.s3.amazonaws.com/release/references/GRCh38/GCA_000001405.15_GRCh38_no_alt_analysis_set.fasta.gz was used for files with input in the FASTQ format. The reference genome at https://broad-references.s3.amazonaws.com/hg38/v0/Homo_sapiens_assembly38.fasta was used with the Ultima data in CRAM format, as this dataset was already aligned to this reference genome.
Running benchmarks on Azure
The script at misc/run_benchmarks.sh was used to run the benchmarks. This orchestrates the localization of the input datasets, references, model files and execution of Snakemake workflows on the machine. The workflow will down-sample the input data to be consistent to run on the Sentieon analysis workflows and will calculate variant calling accuracy against the Genome in a Bottle (GIAB) v 4.2.1 truth set. For the ARM benchmarking we didn’t run ONT and Pacbio data as minimap2 is not support by Sentieon on that architecture in version 202308.01. Support for minimap2 on ARM was added in version 202308.03 of the Sentieon software.
Improved Benchmarking with HBv3
To test the improvement of the software we wanted to retest on the HBv3 series of machines, that we previously recommended. These machines are optimized for applications that are driven by memory bandwidth, such as fluid dynamics, finite element analysis, and reservoir simulation and would be a good fit for Sentieon’s analysis pipelines. Figure 1 presents the runtime and Spot compute cost of running Sentieon’s analysis pipelines for germline variant calling across multiple sequencing technologies on Standard_HB120rs_v3 instance in US East at the time of publication.
Figure 1: Runtime and Spot compute cost of Sentieon DNAseq and DNAscope pipelines on Standard_HB120rs_v3.
Using the Standard_HB120rs_v3, we analyzed 30x Illumina NovaSeq and HiSeqX samples from FASTQ to VCF using the DNAseq and DNAscope pipelines. The DNAseq pipeline took around 28 minutes with a cost of $0.17. Sentieon’s DNAscope pipeline has been speed up and takes only 10 minutes shorter– around 18 minutes with a cost of $0.11, about 6 cents less, see Table 1
The Ultima UG100 dataset is already aligned to the reference genome and pipeline performed variant calling without alignment. The DNAscope pipeline finished in 18 minutes for Spot cost of $0.10.
Sentieon’s DNAscope LongRead pipeline for PacBio HiFi data is more computationally intensive as it includes multiple passes of variant calling along with a read-backed phasing. The DNAscope LongRead pipeline finished in 41 minutes with a Spot cost of $0.25. We add in ONT data in this round of tests, similar to the PacBio data, the ONT pipeline is more computationally involved. The DNAscope LongRead pipeline finished in 88 minutes with a Spot cost of $0.53 with the ONT long reads.
The Element Biosciences AVITI system is supported by a customized Sentieon DNAscope pipeline. Sentieon’s DNAscope pipeline for Element Biosciences finished in 21 minutes with a Spot cost of $0.13.
All run times and costs can be found in Table 1.
Sample
Pipeline
Alignment (min)
Preprocessing (min)
Variant Calling (min)
Total Runtime (min)
On Demand($)
Spot ($)
Element Aviti
DNAscope
11.05
2.30
7.39
20.74
1.241
0.121
Illumina HiSeq X
DNAseq
21.09
2.97
4.11
28.18
1.691
0.171
Illumina HiSeq X
DNAscope
9.47
1.40
7.71
18.57
1.111
0.111
Illumina NovaSeq
DNAseq
21.53
2.63
4.43
28.59
1.721
0.171
Illumina NovaSeq
DNAscope
9.74
1.39
7.78
18.92
1.141
0.111
ONT Duplex
DNAscope
32.91
N/A
55.37
88.28
5.301
0.531
PacBio HiFi
DNAscope
11.49
N/A
29.75
41.24
2.471
0.251
Ultima UG100
DNAscope
N/A
N/A
17.87
17.87
1.071
0.111
Table 1: Runtime and On Demand and Spot compute cost of Sentieon DNAseq and DNAscope pipelines on Standard_HB120rs_v3. Alignment includes alignment with Sentieon BWA-MEM for short-read data and alignment with Sentieon minimap2 for PacBio HiFi and ONT Duplex data. Preprocessing includes duplicate marking, base-quality score recalibration, and merging of multiple aligned files into a single file. Variant calling includes variant calling or variant candidate identification along with variant genotyping and filtering. Variant calling for PacBio HiFi data is implemented as a multi-stage pipeline. All runs were in the eastus region1 Pricing is accurate at the time of publication.
Let’s compare the improvements between v202112.05 and v202308.01 of the software results based on the provided information:
1. DNAseq Pipeline Performance:
– v202112.05: Took around 30 minutes with a cost Spot of $0.18.
– v202308.01: Took around 28 minutes with a cost Spot of $0.17.
– Improvement: In v202308.01, the runtime decreased by 2 minutes; and the cost decreased by $0.01.
2. DNAscope Pipeline Performance:
– v202112.05: Took around 32 minutes with a cost of $0.19.
– v202308.01: Improved to 19 minutes with a cost of $0.11.
– Improvement: In v202308.01, the runtime decreased significantly to 19 minutes, and the cost decreased by $0.07.
3. DNAscope LongRead Pipeline Performance (PacBio HiFi Data):
– v202112.05: Finished in 72 minutes with a Spot cost of $0.42.
– v202308.01: Improved to 41 minutes with a Spot cost of $0.25.
– Improvement: In v202308.01, decreased significantly to 41minutes, and the cost decreased by $0.17.
4. Element Biosciences AVITI System Performance:
– v202112.05: Finished in 31 minutes with a Spot cost of $0.18.
– v202308.01: Improved to 20 minutes with a Spot cost of $0.12.
– Improvement: In v202308.01, the runtime decreased slightly to 20 minutes, and the cost decreased by $0.06.
Overall, in v202308.01, significant improvements were observed in the runtime and cost efficiency of the DNAscope pipeline, whereas minor fluctuations were noted in other pipeline performances. It’s also important to note that v202308.01 introduced support for ONT data in the DNAscope LongRead pipeline.
Sentieon benchmark across multiple instance families and architectures
The Sentieon pipelines and software can scale to smaller or larger instances depending on data as well as instance availability. To provide an accurate representation of performance across various architectures, we again benchmarked the Sentieon DNASeq and DNAscope pipeline with Illumina NovaSeq dataset on ARM and x86 architecture. The runtime, On Demand and Spot compute cost is shown in Figures 2 and 3 respectively. On Demand VMs are pay for compute capacity by the second, with no commitments or upfront payments. While Spot VMs are pay for unused compute capacity at a discount.
Figure 2: Runtime and Dedicated and Spot compute cost of Sentieon DNAseq pipeline across various Azure machine types using Illumina NovaSeq dataset sorted by overall runtime. Larger instances provide lower runtime, while cost is generally consistent within a family but does differ between architectures.
Figure 3: Runtime and Dedicated and Spot compute cost of Sentieon DNAscope pipeline across various Azure machine types using Illumina NovaSeq dataset sorted by overall runtime. Larger instances provide lower runtime, while cost is generally consistent within a family but does differ between architectures.
For the fastest turnaround, the Sentieon DNAseq pipeline can process the Illumina 30x NovaSeq dataset in 28 minutes on a Standard_HB120rs_v3, with a Dedicated cost of $1.72 or a Spot cost of $0.11, see Figure 2. As another cost-effective option, DNAseq can be used on the Standard_D96ads_v5 instance with an On-Demand cost of $3.38, a spot cost of $0.34 and a turnaround time of under 40 minutes, see Figure 2. The DNAscope pipeline for Standard_D96ads_v5 instance with an On-Demand cost of $2.55, a spot cost of $0.26 and a turnaround time of 31 minutes, see Figure 3. Note, for the Standard_F48s_v2, an additional external disk was used to accommodate all the test data for the analysis but wasn’t included in the overall cost.
Let’s compare the performance and cost efficiency between version v202308.01 and v202112.05:
1. DNAseq Pipeline Performance:
– v202112.05: Processed Illumina 30x NovaSeq dataset in 30 minutes on a Standard_HB120rs_v3 with a Spot cost of $0.18.
– v202308.01: Processes the dataset in 28 minutes on a Standard_HB120rs_v3 with a Spot cost of $0.11. Alternatively, it can be processed on a Standard_D96ads_v5 instance in under 40 minutes with a Spot cost of $0.34.
– Improvement: The turnaround time for the Standard_HB120rs_v3 decrased slightly to 28 minutes, with a decrease in Spot cost by $0.07. Additionally, a new option is available on the Standard_D96ads_v5 instance with a slightly longer turnaround time of under 40 minutes but at a higher Spot cost of $0.34 compared to $0.11.
2. DNAscope Pipeline Performance:
– v202112.05: Turnaround time of under 50 minutes with a Spot cost of $0.39.
– v202308.01: Turnaround time of 31 minutes on a Standard_D96ads_v5 instance with an On-Demand cost of $2.55 and a Spot cost of $0.26.
– Improvement: In v202308.01, the turnaround time decreased to 31 minutes, with a Spot cost of $0.26, offering improved performance and cost efficiency compared to the previous version.
3. Comparison Against ARM CPUs:
– v202112.05: ARM runtime was within 10-20 minutes of X86 equivalent for Intel and AMD. Spot price of $0.33 for DNAscope and $0.30 for DNAseq pipeline.
– v202308.01: ARM runtime was within 10-20 minutes of X86 equivalent for Intel and AMD. No significant difference in cost between architectures.
– Improvement: No significant difference in cost between the architectures is noted in v202308.01, whereas in v202112.05, there was a significant difference in cost for AMD architecture compared to Intel.
Overall, in v202308.01, while the DNAseq pipeline on the Standard_HB120rs_v3 shows a slight increase in turnaround time and cost, the DNAscope pipeline on the Standard_D96ads_v5 instance demonstrates improved performance and cost efficiency compared to the previous
version. Additionally, there is no significant difference in cost between ARM and X86 architectures in v202308.01, unlike in v202112.05. We would also like to note that the order of the machine types is slightly different but not with significant changes.
We were able to also run comparison against ARM CPUs. For direct comparison we were able to use the equivalent 32 vCPU machines, but the highest available is 64 vCPU when compared to 96 vCPU in X86 (Figure 2 and 3). In Table 2, we can see that ARM runtime was within 10-20 minutes of X86 equivalent for Intel and AMD. Additionally, Dedicated cost was comparable for DNAscope and DNAseq pipeline comparable across the board. However, this time there was not significant difference in cost between the architectures.
VM Size
Architecture
Pipeline
Total Runtime (min)
On Demand ($)
Spot ($)
D32ds_v5
x86 (Intel)
DNAscope
64.51
1.941
0.191
D32ads_v5
x86 (AMD)
DNAscope
76.95
2.111
0.211
D32pds_v5
ARM
DNAscope
82.00
1.981
0.201
D32ds_v5
x86 (Intel)
DNAseq
121.51
3.661
0.371
D32ads_v5
x86 (AMD)
DNAseq
115.12
3.161
0.321
D32pds_v5
ARM
DNAseq
123.72
2.981
0.301
Table 2: Runtime, Dedicated and Spot compute cost of Sentieon DNAseq and DNAscope pipelines on across 32cpu architectures. All runs were in the eastus region.
1 Pricing is accurate at the time of publication.
These results highlight the ability of the Sentieon software to scale up large instances for faster turnaround and down to smaller instances as needed. We only included a subset of potential compute, based on optimized compute-to-price ratios. However, the Sentieon tools can also be used with other machine families, based on availability in a given region.
Conclusion
Sentieon’s updated DNAseq and DNAscope pipelines are highly scalable and can be used on a variety of machine types. The software can scale up to the 120 vCPU Standard_HB120rs_v3, instances for turnaround times of 28 minutes or down to Standard_D32pds_v5 instances for better pricing on Spot instance of $0.30
If you can get Standard_HB120rs_v3 in your preferred region, it is the cheapest per run. However, if not available, all other Spot pricing options are great with the following two being your best cost advantage, Standard_D32ds_v5 and Standard_D96ds_v5. If you are looking for turnaround time, we recommend any of the 96vCPU options. Sentieon’s FASTQ to VCF pipelines can process Illumina 30x whole genomes for less than $3.60 on On Demand machines or $0.33 on Spot machines and in under 120 minutes. Standard_D32ds_v5 process the DNAseq pipeline in for $3.66 on On Demand machines or $0.37 on Spot machines and in about 121 minutes. While on Spot machines Sentieon DNAseq is capable of processing 30x genomes from FASTQ to VCF with a Spot machine cost of less than $1.50 on a variety of machine types that we tested.
Overall, the new version of the software has decreased cost and, in some cases, decreased turnaround time, with increased performance and range of datasets it can analyze.
Readers should note that all costs represent hardware costs and don’t represent software licensing costs.
To get started with the Sentieon software on Azure, please reach out to info@sentieon.com or visit the Sentieon website at www.sentieon.com
Microsoft Tech Community – Latest Blogs –Read More
Key Architectural Differences Between AWS and Azure Explained
Introduction
In today’s fast-moving digital world, cloud platforms are the foundation of everything from small startups to global enterprises. Choosing the right one can make all the difference when it comes to scalability, security, and driving innovation. With over 94% of companies relying on cloud services, expanding from AWS to Microsoft Azure unlocks a host of new possibilities.
Azure not only provides robust tools and services to optimize your infrastructure, but it also puts you at the forefront of AI advancements. From integrated AI services like Azure OpenAI to sophisticated machine learning models, Azure empowers businesses to transform how they build, deploy, and scale intelligent applications.
This guide explores the key differences between AWS and Azure—covering network architecture, availability zones, security, and more—helping you make informed decisions to future-proof your cloud strategy and stay ahead in an AI-driven world.
1. Network Architecture: AWS VPC vs. Azure VNET
AWS Virtual Private Cloud (VPC)
In AWS, the Virtual Private Cloud (VPC) is the backbone of your network architecture. It lets you build isolated environments where you control every aspect of your networking. The subnets in a VPC must be clearly designated as either public or private, ensuring a firm boundary between internet-facing resources and internal systems. Here’s how AWS VPC handles traffic and segmentation:
AWS VPC Network Segmentation
Key Components:
Public Subnet: Hosts internet-facing resources, such as web servers, which handle incoming HTTP traffic through an Internet Gateway (IGW).
Private Subnet: Hosts internal resources like databases that don’t have direct internet access.
Internet Gateway (IGW): The bridge that provides internet access for public subnets.
VPC Endpoint Gateway: Allows secure, private access to AWS services like S3 and DynamoDB without needing an internet connection.
NAT Gateway: Enables outbound internet traffic from private subnets.
Security Groups and Network ACLs: Provide both stateful and stateless traffic filtering to control inbound and outbound traffic.
Architectural Characteristics:
Explicit Segmentation: Subnets are clearly marked as public or private, making it easy to manage resource placement.
Manual Configuration: Setting up Internet Gateway (IGW), NAT Gateway, and route tables requires hands-on configuration.
Availability Zones (AZs): Resources are often spread across multiple AZs to ensure high availability and fault tolerance.
Azure Virtual Network (VNet)
Azure Virtual Network (VNet) provides similar network isolation as AWS, but with a stronger focus on managed services and simplifying network segmentation. It’s designed to reduce the complexity of manual configuration and make networking more efficient.
Azure VNET Network Segmentation
Key Components:
Public Subnet: Hosts resources that have direct internet access through assigned public IP addresses.
Private Subnet: Holds internal resources and securely connects to Azure services using Private Endpoints through Private Link.
Network Security Groups (NSGs): Control traffic to and from both public and private subnets, ensuring your resources are properly shielded.
Azure NAT Gateway: Offers outbound internet connectivity for resources that don’t have public IPs.
Service Endpoints and Private Links: Enable secure, private access to Azure services without needing to expose your resources to the internet.
Architectural Characteristics:
Streamlined Internet Access: Public IP addresses can be directly assigned to resources, bypassing the need for an Internet Gateway (IGW). Azure’s NAT Gateway provides outbound internet connectivity for private subnets, offering a simpler setup compared to AWS’s NAT Gateway.
Azure NAT Gateway: Offers outbound connectivity for private subnets without public IPs. The setup is simpler compared to AWS’s NAT Gateway, reducing the need for intricate routing configurations.
Integrated Services: Azure emphasizes managed services like Private Link, which simplify complex networking tasks, reducing the need for hands-on management.
Abstraction: Less manual configuration of routing and network appliances, making it easier for organizations to manage.
Key Architectural Differences:
Internet Connectivity:
AWS: Requires an Internet Gateway (IGW) for public subnet internet access.
Azure: Public IPs are directly assigned; no IGW equivalent is needed, and Azure NAT Gateway abstracts much of the internet connectivity configuration.
Subnet Designation:
AWS: Subnets must be explicitly marked as public or private.
Azure: Subnets are neutral; traffic control is handled by NSGs and public IP assignment.
Network Segmentation:
AWS: Provides granular control using Security Groups and NACLs.
Azure: Simplifies this with NSGs and Application Security Groups (ASGs), offering easier management of security rules.
2. Availability Zones and Redundancy
AWS Availability Zones
In AWS, regions are divided into multiple Availability Zones (AZs) to ensure high availability and fault tolerance. Resources can be deployed across these AZs, but it’s not automatic—you need to explicitly distribute them for redundancy, which often involves manual setup.
Multi-AZ architecture ensures redundancy and fault tolerance.
Architectural Approach:
Manual Distribution: Resources must be manually deployed across AZs to achieve redundancy.
Load Balancing: AWS uses Elastic Load Balancers to distribute traffic across multiple AZs for high availability.
High Availability Configurations: For services like RDS, configuring multi-AZ deployments requires additional setup to ensure proper redundancy and failover.
Azure Availability Zones
Azure also provides Availability Zones but takes a different approach by offering automatic zone-redundancy for many services. This abstraction reduces the complexity of managing high availability, especially for managed services. However, it’s important to remember that certain IaaS services, like Azure VMs, still require explicit configuration for redundancy across AZs. Additionally, geo-redundancy (multi-region failover) isn’t automatic for every service and must be configured for mission-critical workloads.
Azure abstracts zone management for many services. It’s zone redundant by default without manual configuration
Architectural Approach:
Automatic Redundancy: Many managed services, like Azure SQL Database, come with built-in zone redundancy by default, saving you the hassle of manual configuration.
Managed Services: Azure abstracts most of the complexity by automatically handling replication and failover for services like Azure SQL Database.
Zone-Aware Services: Not all services in Azure require explicit AZ configurations, making it easier to achieve high availability without manual effort.
Key Architectural Differences:
Resource Deployment:
AWS: Requires manual placement across AZs for redundancy.
Azure: Many services are inherently zone-redundant, though not all services are automatically redundant.
Operational Overhead:
AWS: Achieving high availability often requires more manual configuration.
Azure: Reduces complexity with built-in redundancy for managed services, such as Azure SQL Database, allowing for easier scaling and high availability without additional setup.
3. Security Models: AWS vs. Azure Controls
AWS Security Controls
In AWS, security is managed with a combination of Security Groups (SGs) and Network ACLs (NACLs). Security Groups operate at the instance level, while NACLs control traffic at the subnet level, offering multiple layers of security.
AWS uses SGs for instance-level security and NACLs for subnet-level control.
Key Points:
Security Groups: Manage inbound and outbound traffic by attaching to instances. Since they are stateful, they automatically allow return traffic without the need for additional rules.
Network ACLs: Control traffic at the subnet level and are stateless, meaning both inbound and outbound rules must be defined.
Architectural Implications:
Layered Security: By combining SGs for instance-level control and NACLs for subnet-level control, AWS provides a granular approach to managing traffic.
Complexity: The trade-off is complexity, as you need to manage both SGs and NACLs separately, which can add overhead when configuring security across large deployments.
Azure Security Controls
Azure takes a more streamlined approach to security with Network Security Groups (NSGs) and Application Security Groups (ASGs), making it easier to manage security policies across your infrastructure. Unlike AWS, Azure simplifies the process by combining functionality, reducing the need to manage multiple layers.
Azure simplifies security management through NSGs and ASGs, integrating directly with VMs or network interfaces
Key Points:
NSGs: Control inbound and outbound traffic at both the VM and subnet levels, similar to AWS SGs. Like AWS SGs, NSGs are stateful and automatically allow return traffic.
Flexible Application: NSGs can be applied to subnets, individual VMs, or network interfaces.
ASGs: Offer centralized security rules for logical groupings of VMs, making it easier to manage policies for specific sets of resources.
Dynamic Security Policies: Security rules can reference ASGs, reducing the need to manually update IP addresses whenever new instances are added.
Architectural Implications:
Simplified Management: With NSGs handling both instance-level and subnet-level security, Azure eliminates the need for a separate layer like NACLs, streamlining your security setup.
Efficient Policy Application: ASGs make it easier to apply consistent security policies across groups of VMs without needing to reconfigure individual resources.
Key Architectural Differences:
Security Layers:
AWS: Uses both SGs (stateful) and NACLs (stateless) for security, which can lead to more granular control but requires more effort.
Azure: Primarily uses NSGs (stateful), simplifying the model by not needing an additional layer like NACLs.
Resource Grouping:
AWS: Lacks a direct equivalent to ASGs, though you can use EC2 tagging for dynamic grouping in some cases.
Azure: ASGs allow for more efficient security management by applying centralized policies to logical groupings of VMs.
4. Managed Services: Levels of Automation
AWS Managed Services
AWS offers powerful managed services, but achieving high availability and scaling often requires manual setup. For example, if you want to configure RDS Multi-AZ deployments, you’ll need to manually set up replication across Availability Zones to ensure redundancy.
AWS services provide a high level of control but require more configuration for high availability.
Key Services:
RDS Multi-AZ: Requires manual configuration to enable replication across AZs for high availability.
EC2 Auto Scaling: Involves setting up scaling rules to automatically adjust resources based on demand.
Elastic Load Balancer (ELB): Distributes incoming traffic across AZs but requires additional setup.
Architectural Characteristics:
Customization: AWS gives you full control over configurations, allowing you to tailor setups to your needs.
Operational Responsibility: With more control comes more responsibility—there’s a greater need for hands-on management to ensure high availability and scaling.
Azure Managed Services
Azure takes a different approach by emphasizing automation and built-in redundancy in its managed services. Services like Azure SQL Database and Cosmos DB come with high availability baked in, so you spend less time configuring infrastructure and more time focusing on your core business. However, even though Azure automates much of the infrastructure management, careful planning for failover is still essential, particularly for mission-critical workloads.
Azure services are more abstracted, automating key operational tasks like scaling and availability across zones.
Key Services:
Azure SQL Database: Automatically manages replication, backups, zone redundancy, and scaling without manual intervention.
Azure App Service: Provides a fully managed PaaS solution for web applications, with built-in autoscaling and minimal configuration required.
Azure Cosmos DB: Delivers global replication with automatic scaling, making it easy to build globally distributed applications.
Architectural Characteristics:
Built-In High Availability: Services are designed with resilience in mind, ensuring high availability without additional configuration.
Reduced Operational Overhead: By automating critical tasks like redundancy and scaling, Azure reduces the need for manual maintenance, allowing you to focus on innovation instead of infrastructure management.
Key Architectural Differences:
Control vs. Convenience:
AWS: Offers more control but requires manual configurations to achieve redundancy and scaling, especially across AZs.
Azure: Automates much of the redundancy and scaling, particularly for managed services, with minimal user intervention required.
5. Storage Resiliency and Data Replication
AWS Storage Options
AWS offers a range of storage tiers, each designed for different durability and cost requirements. For instance, S3 Standard replicates data across multiple facilities in a region, providing high durability by default, while S3 One Zone-IA offers a more cost-effective option by storing data in a single Availability Zone (AZ), though this comes with lower durability.
Key Characteristics:
S3 Standard: Automatically replicates data across multiple facilities within a region for high durability.
S3 One Zone-IA: Stores data in a single AZ, reducing cost but sacrificing some resiliency.
Architectural Characteristics:
Automatic Replication: By default, S3 provides high durability across multiple AZs, ensuring data redundancy.
Choice of Redundancy: AWS offers a range of storage classes to allow flexibility in cost and durability, letting users balance redundancy with budget.
Azure Storage Options
Azure gives users more granular control over data replication, offering several replication strategies depending on your needs. Whether you require local, zonal, or geo-redundancy, Azure provides storage options that ensure data availability and resilience.
Key Characteristics:
Locally Redundant Storage (LRS): Keeps three copies of your data within a single data center, ensuring protection against local hardware failures.
Zone-Redundant Storage (ZRS): Replicates data synchronously across three AZs for higher availability.
Geo-Redundant Storage (GRS): Replicates data asynchronously to a secondary region, providing protection against regional failures.
Geo-Zone-Redundant Storage (GZRS): Combines ZRS and GRS for maximum resilience by replicating both within and across regions.
Architectural Characteristics:
Customization: Azure provides multiple levels of control over data replication, letting you choose the redundancy model that best suits your business needs.
Disaster Recovery: Azure includes built-in options for cross-regional replication, giving you out-of-the-box disaster recovery capabilities.
Key Architectural Differences:
Replication Control:
AWS: Automatic multi-AZ replication with fewer options for customization.
Azure: Offers a wider range of replication strategies, including local, zonal, and geo-redundancy, for greater flexibility.
Disaster Recovery Planning:
AWS: Cross-region replication requires additional services and setup.
Azure: Provides built-in geo-redundancy options for simpler disaster recovery planning.
6. Private Connectivity to Cloud Services
AWS VPC Endpoints
In AWS, VPC Endpoints allow you to connect privately to AWS services without exposing your resources to the internet. However, setting up these endpoints requires manual configuration for each service, making it a more hands-on process.
Types:
Gateway Endpoints: Used for services like S3 and DynamoDB.
Interface Endpoints: Powered by AWS PrivateLink to connect to other AWS services.
Architectural Characteristics:
Manual Setup: Each service you want to connect privately to requires its own endpoint, meaning more manual work.
Service-Specific Endpoints: The type of endpoint you need depends on the service, with different setups for gateway versus interface endpoints.
Azure Private Link and Endpoints
Azure streamlines private connectivity with Private Link and Private Endpoints, offering a more unified approach to accessing both Azure services and your own services securely. This reduces the complexity compared to AWS and makes managing private connections more efficient.
Features:
Private Endpoints: These are network interfaces that allow you to privately and securely connect to a service through Azure Private Link.
Service Integration: Works seamlessly with Azure services and can also be used for your own custom applications, creating a more versatile connection model.
Architectural Characteristics:
Simplified Configuration: With a more unified setup, it’s easier to manage and configure private connections in Azure.
Unified Approach: Azure uses the same method—Private Link—to connect to various services, making the process much more consistent and straightforward compared to AWS.
Key Architectural Differences:
Configuration Complexity:
AWS: Requires different setups depending on the type of service, with separate configurations for gateway and interface endpoints.
Azure: Simplifies this with Private Link, providing a unified approach for connecting to multiple services.
Service Accessibility:
AWS: Each service requires a specific endpoint type, which can lead to more management overhead.
Azure: Private Link offers broader access with fewer configurations, making it more user-friendly.
Conclusion
Understanding the key architectural differences between AWS and Azure is crucial for organizations looking to optimize their cloud strategy. While both platforms provide robust services, their approaches to network architecture, availability zones, security models, managed services, and storage resiliency vary significantly. By understanding these distinctions, businesses can fully leverage Azure’s capabilities while complementing their existing AWS expertise, creating a powerful multi-cloud strategy that boosts operational efficiency.
Key Takeaways:
Network Architecture: AWS offers granular control over network segmentation, but Azure simplifies it with integrated managed services, reducing manual configuration.
Availability Zones: Azure’s managed services come with built-in zone redundancy, while AWS often requires more manual intervention to achieve multi-AZ redundancy.
Public Internet Access: AWS uses an Internet Gateway for public internet access, whereas Azure simplifies this by directly assigning public IPs to resources.
Private Subnet Outbound Traffic: Both platforms use NAT Gateways for outbound traffic, but Azure abstracts the configuration more, making it easier to manage.
Security Models: Azure streamlines security with NSGs and ASGs, offering simpler and more flexible traffic control than AWS’s combination of Security Groups and NACLs.
Managed Services: Azure automates critical tasks like redundancy and scaling, while AWS often requires manual configuration for high availability.
Storage Resiliency: Azure provides more granular replication options, while AWS relies on predefined storage tiers.
Private Endpoints: Azure’s Private Link and Endpoints offer a more seamless and integrated approach to private connectivity compared to AWS’s VPC Endpoints, which require more manual setup.
By adapting to these architectural differences, your organization can unlock Azure’s full potential, complementing your AWS expertise and creating a multi-cloud strategy that enhances availability, operational efficiency, and cost management.
Additional resources:
Azure Architecture Guide for AWS Professionals: For a detailed comparison and further reading on transitioning from AWS to Azure.
Mapping AWS IAM concepts to similar ones in Azure: For a direct mapping of AWS IAM concepts to Azure’s security solutions, read this detailed discussion.
Microsoft Tech Community – Latest Blogs –Read More
Inconsistency with health state and drain mode status in host pool
When viewing in the list, health state is not updating, see 2nd VM in this list, shows deallocated, correct, but health state Available
2nd VM in the list when you click into the session host, shows correctly shut down
Also 2nd VM in the list above, shows drain mode off, but when clicked into the session host, drain mode shows on.
using powershell Get-Azwvdsessionhost – seems to match the portal list and shows the host Status as Active and AllowNewSession is True.
Update: After several minutes, these statuses do seem to catch up, but it is at least 10 minutes delayed, maybe more (I didn’t have a clock on it).
Update 2: the user session count returned by the portal and powershell are also incorrect.
When viewing in the list, health state is not updating, see 2nd VM in this list, shows deallocated, correct, but health state Available2nd VM in the list when you click into the session host, shows correctly shut downAlso 2nd VM in the list above, shows drain mode off, but when clicked into the session host, drain mode shows on. using powershell Get-Azwvdsessionhost – seems to match the portal list and shows the host Status as Active and AllowNewSession is True.Update: After several minutes, these statuses do seem to catch up, but it is at least 10 minutes delayed, maybe more (I didn’t have a clock on it). Update 2: the user session count returned by the portal and powershell are also incorrect. Read More
App of chatbot restarts if you leave chatbot and go to normal chat options
Hi All,
I have a chatbot deployed as an app in MS Teams environment, called IT Support, now when we are using the chatbit and a colleague pings you and you respond to colleauge go back to chatbot, the chatbot has restarted even if you come back in matter of 10 seconds.
What settings we can do.
Hi All,I have a chatbot deployed as an app in MS Teams environment, called IT Support, now when we are using the chatbit and a colleague pings you and you respond to colleauge go back to chatbot, the chatbot has restarted even if you come back in matter of 10 seconds. What settings we can do. Read More
What the latest Copilot enhancements mean for Small and Medium-sized Businesses
Hey Everyone! Brenna Robinson, GM for Microsoft 365 small and medium sized businesses, discusses what these latest announcements on the next wave of Copilot could mean for you, highlighting some of the most impactful enhancements.
No matter your business size, I highly recommend the read here!
Would love to hear your thoughts!
Hey Everyone! Brenna Robinson, GM for Microsoft 365 small and medium sized businesses, discusses what these latest announcements on the next wave of Copilot could mean for you, highlighting some of the most impactful enhancements.
No matter your business size, I highly recommend the read here!
Would love to hear your thoughts! Read More
Error in Teams Sorry something went wrong. Please try again or share your feedback.
Hello!
I’m curious if anyone has run into this or may have some insight on how to troubleshoot. Myself and my coworkers have licenses for Copilot 365. We have been using it for several months but in the last week have suddenly started seeing an issue where it seems to be completely disconnected and is throwing “Sorry, something went wrong. Please try again or share your feedback.” within the Meeting Recap (though it will show “AI Notes”), during a meeting that is being transcribed, and strangely just the “work” side of the Windows 11 desktop application gives the error “Sorry, looks like something went wrong.”
We see the same behavior in Teams desktop and web versions.
However, when using Copilot in the regular Teams chat, in the web, or in Microsoft applications it is connected and working as expected.
What could be the disconnect here?
Thanks in advance for any insight!!
Hello! I’m curious if anyone has run into this or may have some insight on how to troubleshoot. Myself and my coworkers have licenses for Copilot 365. We have been using it for several months but in the last week have suddenly started seeing an issue where it seems to be completely disconnected and is throwing “Sorry, something went wrong. Please try again or share your feedback.” within the Meeting Recap (though it will show “AI Notes”), during a meeting that is being transcribed, and strangely just the “work” side of the Windows 11 desktop application gives the error “Sorry, looks like something went wrong.”We see the same behavior in Teams desktop and web versions.However, when using Copilot in the regular Teams chat, in the web, or in Microsoft applications it is connected and working as expected. What could be the disconnect here? Thanks in advance for any insight!! Read More
‘Open-ended’ sequential numbering of Rows in Excel…
I have been looking at the SEQUENCE function but, if I understand it correctly, you need to enter and end point for how many sequential numbers you want Excel to autofill (e.g. 1 to 1000)?
Is there a way to get Excel to autofill a sequential number when new data is entered in a Row?
For example, Column A is sequential numbers starting with ‘1’ (without the ‘ ‘ inverted commas) in A1, then 2 in A2 etc and every time data is entered in a new Row in Column B (for example), a new sequential number is entered automatically in the same Row in Column A? TIA
I have been looking at the SEQUENCE function but, if I understand it correctly, you need to enter and end point for how many sequential numbers you want Excel to autofill (e.g. 1 to 1000)? Is there a way to get Excel to autofill a sequential number when new data is entered in a Row?For example, Column A is sequential numbers starting with ‘1’ (without the ‘ ‘ inverted commas) in A1, then 2 in A2 etc and every time data is entered in a new Row in Column B (for example), a new sequential number is entered automatically in the same Row in Column A? TIA Read More
NEW: Wave 2 updates to Adoption.microsoft.com/Copilt
The work we do as Service Adoption and User Enablement Specialists has never been more important. During this moment, where AI experiences are on the rise, the human connection is essential to helping people overcome their AI anxiety. Our tools, updated this morning to support Wave 2 of our Microsoft 365 Copilot experiences is designed to support you in this journey.
This post will give you all the details of what’s new and available. We’d love to hear your feedback here. How can we assist you further? And don’t forget to take our User Enablement for Copilot course on Microsoft Learn to add the badge to your LinkedIn profile. There are never enough of us that are dedicated to the empowerment of people with technology and your role is paramount in businesses getting the value of the investment they make in these services!
The work we do as Service Adoption and User Enablement Specialists has never been more important. During this moment, where AI experiences are on the rise, the human connection is essential to helping people overcome their AI anxiety. Our tools, updated this morning to support Wave 2 of our Microsoft 365 Copilot experiences is designed to support you in this journey.
Copilot Hub on adoption.microsoft.com
This post will give you all the details of what’s new and available. We’d love to hear your feedback here. How can we assist you further? And don’t forget to take our User Enablement for Copilot course on Microsoft Learn to add the badge to your LinkedIn profile. There are never enough of us that are dedicated to the empowerment of people with technology and your role is paramount in businesses getting the value of the investment they make in these services! Read More
Sensitivity Labels not working as expected
Hi experts,
I’ve been playing with sensitivity labels recently and I’m in testing phase currently having few ppl testing it for me before I officially deploy to all. However, it looks like there are few things that do not work as expected and I’m not sure why. Hope I can find some help here.
Here is what I have configured and what is the experience during our testing
Email should inherit sensitivity label form attachmentI have label for documents set as required , and email is set to no default label and selected “inherit” label from attachmentI have “ConfidentialView Only” label that has allowed only “View rights / Reply / Reply all” allowed permission.Testing experience: When I attach a document with this label assigned, there is no restriction at all and I can forward, download, etc… looks like inheritance of label from attachments to email is not working at all. When I download the attachment, I see that the document has restricted permissions (can’t print, save, etc) so it looks it is working on the document level.“ConfidentialInternal” label should be blockedI can share with external users via SharePoint …and can even open it as external user with no issues at all.. Label access control nor DLP prevents this!!! Is there something I miss here? Not sure if important – I have “MS Entra for Sharepoint enabled”DLP is configured to check Sharepoint, Emails, OneDrive for “ConfidentialInternal” for “content shared outside the organization” and “sensitivity label ConfidentialInternal” and BLOCK itDLP works fine for emails with attachments labelled with this label, and it is blocked as expectedConfidentialInternal is blocked in the outlook when trying to send emailwhen I am sending an attachment with ConfidentialInternal document in Outlook (New Outlook), I see a note about external users that needs to be removed. When trying to send anyway, it is blocked and I get a message below. Which is great
however, another two testers do not get this experience and their email is blocked with DLP (mentioned above) only – which is nice, but the experience I get is much better as users can correct recipients instantly (FYI – I am using NEW Outlook – need to check later this week with the testers if they are on Old or NEW one)
When I go through New Email > Options > Sensitivity – I can see the labels I configured
Hi experts, I’ve been playing with sensitivity labels recently and I’m in testing phase currently having few ppl testing it for me before I officially deploy to all. However, it looks like there are few things that do not work as expected and I’m not sure why. Hope I can find some help here. Here is what I have configured and what is the experience during our testingEmail should inherit sensitivity label form attachmentI have label for documents set as required , and email is set to no default label and selected “inherit” label from attachmentI have “ConfidentialView Only” label that has allowed only “View rights / Reply / Reply all” allowed permission.Testing experience: When I attach a document with this label assigned, there is no restriction at all and I can forward, download, etc… looks like inheritance of label from attachments to email is not working at all. When I download the attachment, I see that the document has restricted permissions (can’t print, save, etc) so it looks it is working on the document level.”ConfidentialInternal” label should be blockedI can share with external users via SharePoint …and can even open it as external user with no issues at all.. Label access control nor DLP prevents this!!! Is there something I miss here? Not sure if important – I have “MS Entra for Sharepoint enabled”DLP is configured to check Sharepoint, Emails, OneDrive for “ConfidentialInternal” for “content shared outside the organization” and “sensitivity label ConfidentialInternal” and BLOCK itDLP works fine for emails with attachments labelled with this label, and it is blocked as expectedConfidentialInternal is blocked in the outlook when trying to send emailwhen I am sending an attachment with ConfidentialInternal document in Outlook (New Outlook), I see a note about external users that needs to be removed. When trying to send anyway, it is blocked and I get a message below. Which is great however, another two testers do not get this experience and their email is blocked with DLP (mentioned above) only – which is nice, but the experience I get is much better as users can correct recipients instantly (FYI – I am using NEW Outlook – need to check later this week with the testers if they are on Old or NEW one) Its a bit of text, and I apologize… Wanted to describe is as best as I can 🙂 … and hopefully help anyone else facing the same… Would be grateful for your help…. As the testing is super time consuming due to the fact that any change I make to sensitivity label and policy, I prefer to wait recommended 24 hrs to see if it had any effect…. Update:forgot to ask, why I see some “default” labels when creating emails? When I go to “More Options”, in new email, I can see the below:When I go through New Email > Options > Sensitivity – I can see the labels I configured Read More
MS Teams Visibility Context
Hi there,
I am developing a Microsoft Teams bot application and am encountering an issue where the bot’s visibility and functionality are not being restricted as specified in the app manifest. Here are the details of the problem.
Issue Description:
Our bot is intended to be used only with the bot itself once sideloaded.We have set the bot’s scope in the manifest to “personal” only.Despite this setting, the bot remains visible and functional in 1:1 chats, group chats and team channels.
Steps Taken:
Updated the manifest.json file to include only “personal” in the bot’s scopes.
Expected Behaviour:
The bot should only be visible and functional in direct interactions with the bot.Users should not be able to add or interact with the bot in 1:1 chats, group chats and team channels.
Questions:
Are there additional steps or configurations required to restrict a bot’s visibility and functionality to direct bot contexts only?Is there a known issue with the manifest scope settings not being enforced for bots?
Here is the manifest:
{
“$schema”:”https://developer.microsoft.com/en-us/json-schemas/teams/v1.16/MicrosoftTeams.schema.json”,
“manifestVersion”:”1.16″,
“version”:”1.2.0″,
“id”:”{{.AppID}}”,
“localizationInfo”:{
“defaultLanguageTag”:”en-gb”,
“additionalLanguages”:[
]
},
“developer”:{
“name”:”REDACTED”,
“websiteUrl”:”REDACTED”,
“privacyUrl”:”REDACTED”,
“termsOfUseUrl”:”REDACTED”
},
“icons”:{
“color”:”color.png”,
“outline”:”outline.png”
},
“name”:{
“short”:”{{.AppName}}”,
“full”:”{{.AppName}}”
},
“description”:{
“short”:”REDACTED”,
“full”:”REDACTED”
},
“accentColor”:”#00bd00″,
“configurableTabs”:[
],
“staticTabs”:[
],
“bots”:[
{
“botId”:”{{.AppID}}”,
“scopes”:[
“personal”
],
“needsChannelSelector”:false,
“isNotificationOnly”:false,
“supportsFiles”:false,
“supportsCalling”:false,
“supportsVideo”:false,
“commandLists”:[
{
“scopes”:[
“personal”
],
“commands”:[
]
}
]
}
],
“composeExtensions”:[
{
“botId”:”{{.AppID}}”,
“commands”:[
{
“id”:”REDACTED”,
“context”:[
“commandBox”,
“compose”,
“message”
],
“description”:”REDACTED”,
“title”:”REDACTED”,
“type”:”action”,
“fetchTask”:true
}
]
}
],
“permissions”:[
“identity”,
“messageTeamMembers”
],
“devicePermissions”:[
],
“validDomains”:[
“REDACTED”,
“REDACTED”
],
“showLoadingIndicator”:false,
“isFullScreen”:false,
“activities”:{
},
“defaultInstallScope”:”personal”
}
Thanks.
Hi there, I am developing a Microsoft Teams bot application and am encountering an issue where the bot’s visibility and functionality are not being restricted as specified in the app manifest. Here are the details of the problem. Issue Description:Our bot is intended to be used only with the bot itself once sideloaded.We have set the bot’s scope in the manifest to “personal” only.Despite this setting, the bot remains visible and functional in 1:1 chats, group chats and team channels.Steps Taken:Updated the manifest.json file to include only “personal” in the bot’s scopes.Expected Behaviour:The bot should only be visible and functional in direct interactions with the bot.Users should not be able to add or interact with the bot in 1:1 chats, group chats and team channels.Questions:Are there additional steps or configurations required to restrict a bot’s visibility and functionality to direct bot contexts only?Is there a known issue with the manifest scope settings not being enforced for bots?Here is the manifest: {
“$schema”:”https://developer.microsoft.com/en-us/json-schemas/teams/v1.16/MicrosoftTeams.schema.json”,
“manifestVersion”:”1.16″,
“version”:”1.2.0″,
“id”:”{{.AppID}}”,
“localizationInfo”:{
“defaultLanguageTag”:”en-gb”,
“additionalLanguages”:[
]
},
“developer”:{
“name”:”REDACTED”,
“websiteUrl”:”REDACTED”,
“privacyUrl”:”REDACTED”,
“termsOfUseUrl”:”REDACTED”
},
“icons”:{
“color”:”color.png”,
“outline”:”outline.png”
},
“name”:{
“short”:”{{.AppName}}”,
“full”:”{{.AppName}}”
},
“description”:{
“short”:”REDACTED”,
“full”:”REDACTED”
},
“accentColor”:”#00bd00″,
“configurableTabs”:[
],
“staticTabs”:[
],
“bots”:[
{
“botId”:”{{.AppID}}”,
“scopes”:[
“personal”
],
“needsChannelSelector”:false,
“isNotificationOnly”:false,
“supportsFiles”:false,
“supportsCalling”:false,
“supportsVideo”:false,
“commandLists”:[
{
“scopes”:[
“personal”
],
“commands”:[
]
}
]
}
],
“composeExtensions”:[
{
“botId”:”{{.AppID}}”,
“commands”:[
{
“id”:”REDACTED”,
“context”:[
“commandBox”,
“compose”,
“message”
],
“description”:”REDACTED”,
“title”:”REDACTED”,
“type”:”action”,
“fetchTask”:true
}
]
}
],
“permissions”:[
“identity”,
“messageTeamMembers”
],
“devicePermissions”:[
],
“validDomains”:[
“REDACTED”,
“REDACTED”
],
“showLoadingIndicator”:false,
“isFullScreen”:false,
“activities”:{
},
“defaultInstallScope”:”personal”
} Thanks. Read More
Microsoft 365 Copilot onboarding hub—where onboarding AI is as intuitive as using it
Securely onboarding AI across an organization can involve several processes. Applying access controls, monitoring integrations with existing infrastructure, managing end user adoption, and more can make the project downright daunting. Add on challenges like staffing shortages and limited in-house AI expertise and you just might decide to put off introducing AI—even a system as valuable as Microsoft 365 Copilot—until tomorrow, or even next month.
At FastTrack for Microsoft 365, we get it.
We also know AI is too important to put off. So, to continue helping admins implement AI across their organizations as seamlessly and responsibly as possible, Microsoft 365 engineers have updated a few key portions of the Microsoft 365 Copilot onboarding hub.
These updates help simplify Microsoft 365 Copilot onboarding processes so you can empower your organization to achieve more with AI quicker and more securely than ever before.
What’s new at the Microsoft 365 Copilot onboarding hub?
The Microsoft 365 Copilot onboarding hub has a fresh look and feel, including an upgraded, modern UI, stateful personalization, and exportable project management.
1. Modern UI
The first thing you may notice is the sleek, new card-based layout that now displays Microsoft 365 Copilot’s Readiness assessment and three setup guides: Quickstart, Foundations+, and Advanced configurations.
2. Microsoft 365 Copilot setup guides: Interactive, personalized, actionable
Don’t let the onboarding hub’s pretty (inter)face fool you though, there’s more value behind those cards than meets the eye. First, here’s a quick run-down of each:
Readiness assessment: Start here to optimize your tailored setup experience. The responses you provide help Copilot’s setup guides determine which tasks you should complete, and in what order, for the safest and most efficient onboarding experience.
Quickstart: In this, Copilot’s most streamlined setup guide, you can safely get Copilot up and running right away, with minimal configuration and customization. If your organization needs a little more time to shore up data hygiene and governance, you can temporarily restrict Copilot search with RSS (Restricted SharePoint Search) while completing those projects.
Foundations+: Build on your Quickstart setup by following steps in the Foundations+ setup guide for fine-tuning data protection settings and readiness options according to your organizational policies.
Advanced configuration: Leverage the full potential of Copilot with advanced security, privacy, and data protection controls. This Advanced configuration guide also provides advanced Microsoft 365 Copilot adoption resources to help you boost end-user engagement.
Each Microsoft 365 Copilot setup guide uses automated wizards with customizable, stateful personalization to lead you, step-by-step, through streamlined, interactive setup experiences.
This means Copilot setup guides are personalized according to your organization’s specific scenarios and requirements, resulting in a unique and highly proficient onboarding experience.
How it works: Information from your Microsoft 365 organization profile, combined with your readiness assessment responses, prepopulates each guide for a comprehensive overview of your organization’s environment. This, coupled with Microsoft’s engineering expertise, allows each setup guide to accurately suggest your next task and lead you through the most efficient and secure path to onboarding Microsoft 365 Copilot.
As you advance and complete tasks, each guide also tracks your progress, accounts for tasks you’ve already finished, and adjusts Microsoft’s next suggested actions accordingly. Look for personalized task tables within the guides as well as suggested action cards at the Copilot onboarding hub.
If you take a break, Copilot’s setup guides remember what steps you’ve already completed and suggest the next recommended task when you return.
For example:
Say you’re an organization that owns E5 licensing and has deployed sensitive data policies—maybe you’re a bank. By responding “Yes” to Copilot’s readiness assessment question, “Does your organization have regulated or sensitive data types?” you might be instructed to review and apply Microsoft Purview best practices next to ensure Microsoft’s strongest security and compliance standards.
On the other hand, you could be a small organization that wants to add Copilot to your Teams subscription primarily to iterate on images. If you respond “No” to the readiness assessment question, “Do you have regulated or sensitive data types?” the guide is likely to minimize your number of basic onboarding steps.
Mature organizations and long-time customers who’ve already deployed several Microsoft 365 products may have already completed Microsoft Purview best practices. If you’re an admin in this scenario, you’ll likely have fewer steps in your Microsoft 365 Copilot onboarding journey. The guides will detect and update previously completed or nonapplicable tasks and highlight your remaining, pertinent tasks.
In another scenario, maybe your organization purchased 100 Microsoft 365 Copilot licenses. You’ve finished assigning them all and have completed every onboarding guide. Back at the Microsoft 365 Copilot onboarding hub, you may find personalized suggested action cards to guide you on next steps. For example:
3. Expanded project management for your Microsoft 365 Copilot onboarding tasks
We know admins rely on integrated and comprehensive project management tools to assign tasks, set deadlines, and track setup progress. To help make your job easier, Microsoft engineers have streamlined project management too.
Now you can find workload monitoring inside each Microsoft 365 Copilot setup guide that is:
Assignable: Easily distribute tasks among team members.
Trackable: Keep an eye on progress.
Schedulable: Set deadlines and timelines.
Exportable: Track Copilot onboarding tasks outside of the hub.
The option to export task management is a new and practical update. To carry it out, simply place task information into a CSV, and then import the information to your usual project management software.
Why use FastTrack for Microsoft 365 resources to onboard Copilot?
Can we set up and onboard Microsoft 365 Copilot manually instead, by following a Microsoft Learn article? you might wonder.
Yes, you can. In fact, Microsoft Learn articles are valuable, comprehensive resources for anyone looking to understand Microsoft technologies. They’re also freely accessible and kept up to date.
However, Learn articles are static resources with universal guidance and information that’s applicable to many different industries and user environments. Following them to onboard Microsoft 365 Copilot across your organization involves interpreting which tasks and best practices apply to your specific environment and then making sure you’ve fulfilled each one.
Microsoft 365 Copilot setup guides: a more efficient and secure way to onboard AI
Aligned with Microsoft’s commitment to making AI broadly and responsibly available—thereby empowering every person and every organization on the planet to achieve more—Microsoft engineers have designed Microsoft 365 Copilot automated setup guides to be:
Tailored to your current state: From a panoramic vantage point, each Microsoft 365 Copilot setup guide assesses your organization’s environment to curate the most relevant onboarding and configuration path for you. This allows for pointed, prescriptive recommendations you can rely on.
Incorporated with Microsoft best practices: You’ll get a smooth, guided setup experience with prepopulated information and step-by-step instructions defined by Microsoft experts for an optimal setup experience.
Streamlined: You’ll know you’re prioritizing the correct order of operations as you progress through your Microsoft 365 Copilot onboarding journey. You won’t have to worry whether you’ve made a wrong move or missed a helpful resource.
Comprehensive: Should you need additional onboarding or adoption resources, Copilot’s guides will connect you to the right resource at the right point in your setup journey.
Make the Microsoft 365 Copilot onboarding hub your destination for onboarding AI
With modern UI, improved automation, and new capabilities, the Microsoft 365 Copilot onboarding hub and setup guides offer a faster and safer way to onboard AI.
Replace guesswork and wasted time with efficiency and security.
Feel confident you’re onboarding AI responsibly.
Shorten your time to discovering value with Microsoft 365 Copilot.
Head over to the Microsoft 365 Copilot onboarding hub and empower your end users to achieve more today, instead of waiting until tomorrow.
Navigating to the Microsoft 365 Copilot onboarding hub
Bookmark the Microsoft 365 Copilot onboarding hub for quickest access or navigate there by following these instructions:
Sign in to the Microsoft 365 admin center.
Follow Setup from the side menu and select Advanced deployment guides & assistance.
Scroll down or filter guides by Product and select Set up Microsoft 365 Copilot.
This takes you directly to Setup Microsoft 365 Copilotopilot for Microsoft 365, your Microsoft 365 Copilot onboarding hub. You’ve arrived!
Need onboarding assistance?
Customers with eligible licenses can submit a request for assistance to FastTrack for help onboarding Copilot.
Microsoft Tech Community – Latest Blogs –Read More
Office LTSC 2024 is now available
Microsoft 365 offers the cloud-backed apps, security, and storage that customers worldwide rely on to achieve more in a connected world – and lays a secure foundation for leveraging generative AI to go even further. Investing in our cloud productivity solutions and the AI-powered innovation they support will continue to be Microsoft’s priority.
Still, we know that some customer scenarios require a different approach. Some devices must never be connected to the internet; others need to remain unchanged for years at a time. We remain committed to supporting our customers and these scenarios. Earlier this year, we offered a public preview of Microsoft Office Long Term Servicing Channel (LTSC) 2024. Today, we’re announcing the general availability of this next perpetual version of Office for commercial and government customers.
An updated solution for specialized needs
Office LTSC 2024 offers a locked-in-time version of familiar productivity tools, updated with a subset of the features that have been added to Microsoft 365 Apps for enterprise over the last three years. New features for this release include Dynamic Charts and more than a dozen new text and array functions in Excel, enhanced search and meeting creation options in Outlook, and improvements to performance, security, and accessibility. Learn more about what’s new.
Office LTSC 2024 will be supported for five years under the Fixed Lifecycle Policy, and – like prior versions – will be deployable alongside Microsoft 365 Apps using a common set of tools to enable customers to more easily manage hybrid environments. Learn more about how to deploy and manage Office LTSC at Overview of Office LTSC 2024.
Choosing the best productivity suite for your organization
While Office LTSC 2024 offers many significant improvements over the previous Office LTSC release, as an on-premises product it does not include the cloud-based capabilities of Microsoft 365 Apps, like real-time collaboration, AI-driven automation, or cloud-backed security and compliance capabilities. And for customers who need additional flexibility on deployment and connectivity – but not a fully disconnected solution – Microsoft 365 has options that can help. For example, device-based licensing can simplify management of Microsoft 365 Apps in settings like computer labs or hospitals where devices are shared by many users. And extended offline access can be used to maintain access to Microsoft 365 Apps on devices that need to be disconnected from the internet for up to six months at a time. Microsoft 365 (or Office 365) is also required to subscribe to Microsoft 365 Copilot; as a disconnected product, Office LTSC does not qualify.
Microsoft 365 Apps [1]
Office LTSC 2024
Apps included
Word, Excel, PowerPoint, Outlook, OneNote, OneDrive, Microsoft Access (Windows Only), Microsoft Publisher (Windows Only) [2], Sway, Microsoft Forms
Word, Excel, PowerPoint, Outlook, OneDrive, OneNote, Microsoft Access (Windows Only) [3]
Desktop apps
Premium apps installed on up to 5 PCs or Macs
Classic apps installed on 1 PC or Mac
Mobile apps
Create & edit on up to 5 phones + 5 tablets
Web apps
Create & edit online
Eligible for Microsoft 365 Copilot add-on [4]
Cloud storage
1 TB per user
Feature updates
New features and security updates delivered via Current, Monthly, or Semi-Annual channels
Security updates only
Shared devices
Shared computer activation or device-based licensing available
Device-based licensing only
Connectivity requirements
Internet connection required for activation, license validation, and internet-based functionality. Extended offline access available to enable devices to stay disconnected for up to six months at a time.
No internet connection required
Embracing the future of work
Microsoft 365 offers the most secure, productive, and cost-effective solution for most organizations, and positions customers to unlock the transformative power of AI with Microsoft 365 Copilot. Especially as we approach the end of support for Office 2016 and Office 2019 on October 14, 2025, we encourage customers still using these solutions to transition to a Microsoft 365 subscription that suits their needs as a small business or a larger organization. And for scenarios where that is not possible – where a disconnected, locked-in-time solution is required – this new release reflects our commitment to supporting that need.
Learn more
Office LTSC 2024 is available to existing commercial and government volume-licensed customers today, along with new on-premises versions of Project and Visio. These products will be generally available to all customers on October 1. We will share more about Office 2024 for consumers in the coming weeks. For more information about Office LTSC 2024 and how it compares to Microsoft 365 Apps for enterprise, please visit the Office LTSC plan comparison page. If your organization is ready to take the next step toward the AI-powered future, find out how to get started with Microsoft 365 today.
Notes:
[1] Applies to Microsoft 365 Apps for enterprise and Microsoft 365 Apps for business. All Microsoft 365 and Office 365 suites that include desktop apps also include everything listed here – and more. Learn about the available options.
[2] Microsoft Publisher will be retiring in October 2026.
[3] Microsoft Access is included only with Office LTSC Professional Plus.
[4] Microsoft 365 Copilot may not be available for all markets and languages. To purchase, customers must have a qualifying Microsoft 365 plan for enterprise or business.
Microsoft Tech Community – Latest Blogs –Read More
Gelombang Kedua Microsoft Copilot: Pages, Python di Excel, dan Agents
Read the English version here.
Hari ini kami meluncurkan gelombang berikutnya dari Microsoft 365 Copilot, menyatukan web + work + Pages sebagai sistem desain yang betul-betul baru untuk bekerja.
Pertama, Business Chat adalah pola kerja baru yang mengubah semua konten organisasi Anda menjadi database yang kaya akan informasi dan insights, memungkinkan Anda berkolaborasi dengan Copilot seperti partner. Business Chat membawa data yang ada di web dan data dari pekerjaan Anda ke dalam Copilot Pages – sebuah artefak digital pertama untuk era AI.
Kedua, kami melakukan transformasi pada Copilot di aplikasi Microsoft 365. Pelanggan kami memberi tahu kami bagaimana Copilot in Teams telah mengubah pengalaman rapat selamanya. Faktanya, pengalaman ini menjadi pengalaman dengan nilai tertinggi dari semua pengalaman yang Copilot hadirkan. Kini, kami senang dapat melakukan hal yang sama untuk analisis data tingkat advanced di Excel, storytelling dinamis di PowerPoint, mengelola kotak inbox Anda di Outlook, dan masih banyak lagi.
Ketiga, kami memperkenalkan Copilot agents, memudahkan dan mempercepat proses automasi serta proses operasional bisnis Anda – memungkinkan Anda untuk meningkatkan kapabilitas tim Anda.
Kami senang dapat membagikan pembaruan ini dengan pelanggan kami di seluruh dunia. Dari perusahaan besar hingga bisnis berskala kecil, mereka setiap harinya membantu Copilot menjadi lebih baik. Hampir 1.000 pelanggan telah memberikan feedback langsung seputar Copilot. Sejak Copilot tersedia secara umum, kami telah menghadirkan lebih dari 150 fitur dan kemampuan baru. Kini dengan GPT4o dan orkestrasi yang semakin meningkat, kami meningkatkan kinerja Copilot secara signifikan. Rata-rata, respons Copilot menjadi lebih dari dua kali lebih cepat, dan tingkat kepuasan telah meningkat hampir 3X*. Saat Anda menggabungkan semua ini, kami telah membangun feedback loop AI terbaik di dunia dengan Copilot. Dan kami akan terus membawa semua model terbaru ke Copilot dengan cepat, meningkatkan kapabilitas produk berdasarkan masukan Anda dengan cepat, serta menambahkan kemampuan baru dan model baru, termasuk OpenAI o1 dengan kemampuan penalaran lanjutan.
Memperkenalkan Copilot Pages—artefak digital baru untuk era AI
Copilot adalah antarmuka (UI) baru untuk AI. Ini semua dimulai dengan BizChat, pusat jaringan (central hub) yang menggabungkan semua data Anda—data web, data kerja, dan data lini bisnis—langsung ke dalam alur kerja Anda. BizChat merupakan tempat Anda dapat bekerja dengan Copilot seperti partner, merealisasikan nilai dari semua konten di organisasi Anda, sehingga setiap artefak menjadi aset bisnis yang dapat digunakan kembali. Hari ini, kami mengumumkan Copilot Pages, sebuah kanvas dinamis dan persisten di BizChat, yang dirancang untuk kolaborasi AI multiplayer. Ini adalah langkah pertama dalam sistem desain baru kami untuk knowledge work.
Dengan Pages, semua data di organisasi Anda—baik yang dibuat oleh manusia atau AI—menjadi persisten, dapat diakses, dan berharga. Pages mengambil konten hasil produksi AI yang bersifat sementara dan membuatnya tahan lama, sehingga Anda dapat mengeditnya, menambahkannya, dan membagikannya dengan orang lain. Anda dan tim Anda dapat bekerja secara kolaboratif dalam sebuah page dengan Copilot, melihat pekerjaan semua orang secara real time, dan beriterasi dengan Copilot seperti partner; menambahkan lebih banyak konten dari data Anda, file, dan web ke Page Anda. Ini adalah pola kerja baru yang sesungguhnya—multiplayer, kolaborasi manusia ke AI ke manusia. Untuk pelanggan Microsoft 365 Copilot, Pages mulai diluncurkan hari ini, dan akan tersedia secara umum akhir September 2024 mendatang.
Dalam beberapa minggu mendatang, kami juga akan membawa Pages ke lebih dari 400 juta orang yang memiliki akses ke Microsoft Copilot versi gratis, saat mereka sign in dengan akun Microsoft Entra—menawarkan kombinasi pengalaman web (web grounding), perlindungan data Perusahaan (Enterprise Data Protection), dan Pages. Hari ini, Anda dapat mencoba Microsoft Copilot di Microsoft.com/copilot, serta menyematkan Copilot langsung ke dalam alur kerja Anda di aplikasi Microsoft 365, dan segera, di Outlook serta Teams.
Meningkatkan produktivitas dengan Copilot
Bagi jutaan orang di seluruh dunia, pekerjaan terjadi di aplikasi Microsoft 365. Di situlah bekerja bersama Copilot sudah menjadi kebiasaan sehari-hari, memberikan manfaat dari sisi produktivitas pribadi dan penghematan waktu. Dengan Gelombang Kedua, kami mengambil semua yang kami pelajari dari pelanggan kami dan menggunakannya untuk membuat Copilot menjadi lebih baik lagi.
Copilot in Excel
Ketika orang ingin bekerja dengan data dan mendapatkan nilai nyata dari data tersebut, mereka beralih ke Excel—ini adalah antarmuka untuk semua data bisnis Anda. Hari ini, kami senang dapat mengumumkan bahwa Copilot in Excel sekarang tersedia secara umum. Kini, Anda dapat bekerja dengan data yang belum diformat dalam bentuk tabel. Kami telah menambahkan keterampilan baru untuk memanfaatkan kekuatan optimal Excel, dengan dukungan bagi lebih banyak rumus/formula seperti XLOOKUP dan SUMIF; pemformatan bersyarat; dan kemampuan untuk beriterasi dengan Copilot pada visualisasi seperti grafik dan PivotTable, agar sesuai dengan berbagai kebutuhan Anda. Copilot di Excel sekarang juga dapat bekerja dengan teks, selain dengan data numerik.
Kami bahkan telah melangkah lebih jauh. Hari ini, kami mengumumkan Copilot in Excel dengan Python, menggabungkan kekuatan Python—salah satu bahasa pemrograman untuk bekerja dengan data paling populer di dunia—dengan Copilot in Excel. Sekarang, siapapun dapat bekerja dengan Copilot untuk melakukan analisis lanjutan seperti forecasting, analisis risiko, machine learning, dan memvisualisasikan data kompleks—semua menggunakan bahasa sehari-hari, tanpa memerlukan pemrograman/coding. Ini seperti memiliki tambahan data analyst yang terampil di tim. Copilot in Excel dengan Python saat ini tersedia dalam versi pratinjau publik (public preview).
Copilot in PowerPoint
Tidak ada yang dapat mengubah ide menjadi presentasi rapi hanya dalam satu prompt. Sekarang, tersedia secara umum, Narrative builder di PowerPoint membantu Anda bekerja dengan Copilot seperti partner, beriterasi bersama untuk membangun draf pertama yang menarik dalam hitungan menit, sambil tetap mengendalikan proses kreatif. Copilot menggunakan prompt Anda untuk membangun outline dengan topik yang dapat Anda edit dan perbaiki untuk membuat draf pertama presentasi Anda. Segera, Anda akan dapat menambahkan file ke outline untuk memperkuat landasan topik Anda. Dan dengan Brand manager, Copilot dapat memanfaatkan template brand perusahaan Anda, sehingga presentasi Anda siap digunakan untuk perusahaan dan sesuai brand yang diwakilkan. Segera, Copilot akan dapat menyertakan gambar yang disetujui perusahaan dari SharePoint Organization Asset Library Anda.
Copilot in Teams
Dalam berbagai rapat, ada dua percakapan penting: yang diucapkan, dan yang terjadi di chat. Copilot in Teams sekarang dapat menalar transkrip serta chat rapat untuk memberi Anda gambaran lengkap tentang apa yang dibahas. Misalnya, Anda dapat meminta Copilot untuk memberitahukan apakah ada pertanyaan yang Anda lewatkan dalam rapat. Copilot akan dengan cepat memindai apa yang dikatakan peserta rapat, serta apa yang diketik dalam chat, untuk melihat apakah ada yang tidak terjawab. Sekarang dengan Copilot in Teams, tidak ada pertanyaan, ide, atau kontribusi yang tertinggal. Fitur ini tersedia secara umum mulai bulan ini.
Copilot in Outlook
Kita semua berkutat dengan terlalu banyak email. Sekarang, dengan Prioritize my inbox, Copilot in Outlook membantu Anda menemukan pesan yang penting dengan cepat, menganalisis inbox Anda berdasarkan konten email dan role Anda—seperti siapa atasan Anda dan thread email mana yang Anda selama ini telah responsif. Tidak perlu lagi menyaring pesan panjang—Copilot secara otomatis menghasilkan ringkasan singkat dari setiap email dan menyertakan alasan mengapa pesan tersebut diprioritaskan, bersama dengan insights utama. Segera, Anda akan dapat mengajarkan Copilot topik, kata kunci, atau orang tertentu yang penting bagi Anda; memastikan email tersebut ditandai sebagai prioritas tinggi. Fitur-fitur ini akan mulai tersedia dalam versi pratinjau publik mulai akhir 2024.
Copilot in Word
Saat bekerja di Word, Anda sering kali perlu membawa konten dari dokumen dan aplikasi lain. Namun, mencari dan menggabungkan informasi yang Anda butuhkan, bisa memakan waktu dan mengganggu penulisan Anda. Mulai tersedia akhir bulan ini, Copilot in Word akan memungkinkan Anda merujuk tidak hanya data dari web; data kerja seperti Word, PowerPoint, PDF; dan dokumen terenkripsi; tetapi juga data email dan rapat. Seluruh pengintegrasian informasi ini langsung disertakan ke dalam alur kerja Anda, sehingga Anda dapat menyelesaikan draf pertama yang baik dengan cepat. Copilot in Word adalah partner menulis yang baik. Pembaruan terbaru meliputi on-canvas start experience dengan rekomendasi prompt untuk memulai proses kreatif Anda, dan kemampuan untuk berkolaborasi dengan Copilot saat Anda mengerjakan bagian tertentu dari dokumen Anda – keduanya tersedia secara umum.
Copilot in OneDrive
OneDrive adalah sebuah repositori lengkap di mana para profesional menyimpan konten kerja pribadi mereka—tetapi kita semua menghabiskan terlalu banyak waktu untuk mencoba menemukan dokumen yang tepat atau mengingat dokumen mana yang memiliki konten yang kita butuhkan. Copilot in OneDrive dapat menalar semua file Anda dengan cepat untuk menemukan informasi yang Anda butuhkan, memudahkan Anda untuk mendapatkan insights, merangkum file, dan membandingkan hingga lima file dengan ringkasan yang jelas serta mudah dibaca, tentang detail dan perbedaan dalam masing-masing file tanpa membuka file tersebut. Copilot in OneDrive sekarang mulai di-roll out, dan akan tersedia secara umum pada bulan ini.
Meningkatkan kapabilitas tim Anda dengan Copilot agents
Mempercepat setiap proses bisnis dengan Copilot—untuk meningkatkan pendapatan dan mengurangi biaya—adalah cara terbaik memperoleh keunggulan kompetitif di era AI. Memperkenalkan Copilot agents, yang sekarang tersedia secara umum. Agents adalah asisten AI yang dirancang untuk mengotomatisasi dan menjalankan proses bisnis, bekerja dengan atau untuk manusia. Kapabilitas mereka beragam, dari agent sederhana yang bekerja dengan format prompt-dan-respons, agent yang menggantikan tugas berulang, hingga agent yang lebih advanced dan otonom. Dengan Copilot agents, Anda dapat melakukan semua ini dan bahkan lebih banyak lagi, dengan membawa kekuatan agent langsung ke dalam alur kerja Anda. Copilot agents bekerja untuk Anda di balik layar, sepenuhnya dikelola dan diorkestrasikan oleh Copilot. Sederhana dan aman untuk dikelola, semua Copilot agents memiliki prinsip Responsible AI dan janji yang sama—data Anda tidak pernah meninggalkan batas kepercayaan Microsoft 365, dan semuanya terjadi dalam tenant Anda. Anda juga dapat memanfaatkan agent yang sudah dibangun sebelumnya seperti Visual creator agent, AI yang membantu Anda membuat gambar, desain, dan (segera) video.
Untuk mempermudah pengembangan Copilot agents, hari ini kami mengumumkan agent builder, pengalaman baru dan sederhana yang didukung oleh Copilot Studio.
Sekarang, siapapun dapat membuat Copilot agent langsung di BizChat atau SharePoint dengan cepat, merealisasikan nilai dari repositori pengetahuan luas yang disimpan dalam file SharePoint Anda. Bayangkan, misalnya, menggunakan agent builder untuk membangun agent langsung di alur kerja Anda di BizChat, menghubungkannya ke SharePoint untuk memberdayakannya dengan data proses bisnis yang relevan secara cepat, dan dalam beberapa saat Anda sudah memiliki sumber daya pengetahuan kuat yang dapat Anda bagikan dengan kolega Anda di Teams ataupun Outlook. Anda dapat me-mention agen (dengan @mention) seperti Anda me-mention rekan kerja Anda yang lain, berbagi informasi baru, dan mengajukan pertanyaan yang dapat agent Anda jawab secara real time. Jika Anda ingin mengembangkan agent yang lebih advanced dari sana, Anda dapat menyesuaikannya lebih lanjut di Copilot Studio, men-deploy-nya untuk melakukan hal-hal seperti menghubungkan Anda ke sumber data, atau mengambil tindakan tertentu atas nama Anda.
Copilot agents dan agent builder di BizChat akan diluncurkan secara umum kepada semua pelanggan dalam beberapa minggu mendatang. Copilot agents dan agent builder di SharePoint akan memasuki versi pratinjau publik pada awal Oktober.
Pelanggan memperoleh beragam manfaat dari Copilot
Selama 18 bulan terakhir, bekerja dengan Copilot telah menjadi kebiasaan sehari-hari bagi orang-orang di mana saja, membantu mereka menyelesaikan tugas lebih cepat, mengadakan rapat yang lebih bermakna, berkolaborasi lebih efektif, dan menyederhanakan proses bisnis. Pelanggan Copilot tumbuh lebih dari 60 persen dari kuartal ke kuartal, sementara jumlah orang yang setiap harinya menggunakan Copilot di tempat kerja telah berlipat ganda. Hari ini, kami mengumumkan bahwa Vodafone menginvestasikan Copilot bagi 68.000 karyawan. Amgen menggunakan Copilot untuk mempercepat penelitian tentang penyakit langka. Agen layanan pelanggan di Teladoc menghemat hingga lima jam setiap minggunya setelah menggunakan Copilot untuk menyusun respons terhadap pertanyaan umum klien. Marketers di Finastra menggunakan Copilot untuk beralih dari ideasi konten ke proses produksi 75 persen lebih cepat. Rata-rata, pengguna Copilot di Honeywell menghemat 92 menit per minggu setelah menggunakan Microsoft 365 Copilot, setara dengan 74 jam selama satu tahun penuh penggunaan**.
“Dulunya, ketika kami membangun kampanye besar seperti kampanye Finance is Open, kami memerlukan waktu tiga bulan untuk menghasilkan konten kampanye tersebut. Sekarang, kami bisa melakukannya dengan Copilot dalam waktu kurang dari satu bulan”. – Joerg Klueckmann, Head of Corporate Marketing & Communications, Finastra
Melihat ke Depan
Hari ini adalah permulaan dari gelombang kedua inovasi Copilot—dalam dua bulan ke depan, kami akan berbagi lebih banyak lagi tentang bagaimana Copilot meningkatkan produktivitas dan mempercepat nilai bisnis bagi setiap pelanggan. Stay tuned.
Mulailah menggunakan Copilot hari ini—kunjungi Microsoft365.com/copilot atau unduh aplikasi Microsoft 365 di perangkat seluler Anda.
Untuk insights dari riset terbaru mengenai masa depan pekerjaan dan generative AI, kunjungi WorkLab.
###
*Di antara respons Copilot dalam Bahasa Inggris
**Statistik berasal dari internal survei Honeywell terhadap 5.000 karyawan, dengan 611 di antaranya merespons.
HP print drivers
Hello I just bought a brand new surface 11th edition. And I am trying to download the printer drivers but my surface is throwing missing plug play or inf errors. I had hp printer support try to help me but it seems not to work on the surface end as all my other computers connect fine. 2/3 surfaces that work out of that office cannot print to the laser jet 4301 fdw printer why?
Heres what I know…
Surface 11 runs on a AWD processor.
So i tried the universal AWD installer but nothing
general installers say the surface doesnt have the plug play installed
and another universal installer said that it doesnt have the correct infs
Hello I just bought a brand new surface 11th edition. And I am trying to download the printer drivers but my surface is throwing missing plug play or inf errors. I had hp printer support try to help me but it seems not to work on the surface end as all my other computers connect fine. 2/3 surfaces that work out of that office cannot print to the laser jet 4301 fdw printer why? Heres what I know… Surface 11 runs on a AWD processor. So i tried the universal AWD installer but nothinggeneral installers say the surface doesnt have the plug play installedand another universal installer said that it doesnt have the correct infs Read More
Detecting Palindromes using Copilot for Excel
Hi everyone, over the last few weeks we have had a series of posts to show you some of the things that are possible to do with Copilot in Excel. Today I have a list of words and would like to detect which ones are Palindromes. What is a Palindrome? A Palindrome is a word or sequence of characters that is the same backwards and forwards.
To get started, I ask Copilot:
Add a column to indicate whether the words are palindromes
Looking at B2:B88, here’s 1 formula column to review and insert in Column C:
Is Palindrome
Determines whether each word is a palindrome by checking if the word reads the same backward as forward, and returns “Yes” or “No” accordingly.
=IF([@Words]=TEXTJOIN(“”,,MID([@Words],SEQUENCE(LEN([@Words]),1,LEN([@Words]),-1),1)),”Yes”,”No”)
I’m not sure what the formula is doing, so I click on the “Show explanation” dropdown and it says:
Determines whether each word in the “Words” column is a palindrome by using the following steps:
Uses the SEQUENCE function to generate a sequence of numbers from the length of the word down to 1.
Uses the MID function to extract each character of the word in reverse order based on the sequence generated.
Uses the TEXTJOIN function to concatenate the reversed characters into a single string.
Compares the original word with the reversed string using the IF function.
Returns “Yes” if the word is a palindrome and “No” otherwise.
The suggested formula column sounds like it is doing the right thing, so I click on the button to insert the column:
Over the coming weeks I will continue to share more examples of what you can do with Copilot in Excel.
Thanks for reading,
Microsoft Excel Team
*Disclaimer: If you try these types of prompts and they do not work as expected, it is most likely due to our gradual feature rollout process. Please try again in a few weeks.
Hi everyone, over the last few weeks we have had a series of posts to show you some of the things that are possible to do with Copilot in Excel. Today I have a list of words and would like to detect which ones are Palindromes. What is a Palindrome? A Palindrome is a word or sequence of characters that is the same backwards and forwards.
List of words: airplane, apple, backpack, banana, bed, bib, boat, book, bottle, building, bus, camera, car, chair, civic, clock, cloud, coffee, computer, dad, deed, deified, deleveled, desk, detartrated, door, eye
To get started, I ask Copilot:
Add a column to indicate whether the words are palindromes
Copilot in Excel pane with the above prompt
Looking at B2:B88, here’s 1 formula column to review and insert in Column C:
Is Palindrome
Determines whether each word is a palindrome by checking if the word reads the same backward as forward, and returns “Yes” or “No” accordingly.
=IF([@Words]=TEXTJOIN(“”,,MID([@Words],SEQUENCE(LEN([@Words]),1,LEN([@Words]),-1),1)),”Yes”,”No”)
I’m not sure what the formula is doing, so I click on the “Show explanation” dropdown and it says:
Determines whether each word in the “Words” column is a palindrome by using the following steps:
Uses the SEQUENCE function to generate a sequence of numbers from the length of the word down to 1.
Uses the MID function to extract each character of the word in reverse order based on the sequence generated.
Uses the TEXTJOIN function to concatenate the reversed characters into a single string.
Compares the original word with the reversed string using the IF function.
Returns “Yes” if the word is a palindrome and “No” otherwise.
The suggested formula column sounds like it is doing the right thing, so I click on the button to insert the column:
Table with 2 columns containing the list of words and a new “Is Palindrome” column with Yes and No values to indicate if it is a palindrome
Over the coming weeks I will continue to share more examples of what you can do with Copilot in Excel.
Thanks for reading,
Microsoft Excel Team
*Disclaimer: If you try these types of prompts and they do not work as expected, it is most likely due to our gradual feature rollout process. Please try again in a few weeks.
Read More