Exciting AzureR Updates Unveiled for May/June: Revolutionizing the Way You Work

“Exciting AzureR Updates Unveiled for May/June: Revolutionizing the Way You Work”

Introduction:

Welcome to the summary of the updates to AzureR family of packages in May and June 2021. In this summary, we will cover the updates to AzureAuth, AzureGraph, AzureRMR, AzureStor, and Microsoft365R packages.

Firstly, in AzureAuth, we have made some changes to the default caching behavior, added a function to manually create a caching directory, and updated the Shiny vignette.

Moving on to AzureGraph, we have enhanced support for the paging API and introduced a new class for iterating through the pages in the result. We have also added support for the batch request feature and included new methods to list users, groups, apps, and service principals. Additionally, there is a new vignette on authentication.

In AzureRMR, we have a new vignette on authentication, updated the Resource Manager API version, and improved the handling of the response format in the list locations function.

In AzureStor, we have added support for generating a service SAS, fixed compression issues, resolved a bug in the list blobs function, and made updates to the client API version.

Lastly, in Microsoft365R, we have added new features for OneDrive/SharePoint, Outlook, and Teams. These features include methods for accessing shared items, getting drives by name, deleting non-empty folders, searching emails, and interacting with teams and channels.

For more information on these updates, please refer to the respective vignettes and documentation. Stay updated with the latest features and improvements in the AzureR packages to enhance your Azure experience.

Full Article: “Exciting AzureR Updates Unveiled for May/June: Revolutionizing the Way You Work”

AzureR Package Updates May and June 2021

In the months of May and June 2021, the AzureR family of packages received several updates. These updates aim to enhance the functionality and performance of the packages. This news report provides a summary of the updates made to each package during this period.

AzureAuth

The AzureAuth package underwent some changes. The default caching behavior was modified to disable the cache when running inside Shiny. Additionally, the Shiny vignette was updated to clean up the redirect page after authenticating. Thanks to Tyler Littlefield for this contribution. Furthermore, a new function called “create_AzureR_dir” was introduced. This function allows users to manually create the caching directory. It is particularly useful for non-interactive sessions, as well as Jupyter and R notebooks, which do not have a console prompt for user input.

AzureGraph

The AzureGraph package now offers enhanced support for the paging API. Many Graph calls return lists of objects divided into pages. The first response contains a subset of the full list along with a link to the next subset. To handle this, AzureGraph introduced the “ms_graph_pager” R6 class, which serves as an iterator for the pages in the result. All “list_*” R6 methods were rewritten to utilize this class. Additionally, these methods now have the options to filter the result set and cap the number of results. The package also added support for the batch request feature. By using the “graph_request” R6 class and the “call_batch_endpoint” function, users can pass multiple calls to the API and get the results back in a single response. For more information on these APIs, refer to the “Batching and Paging” vignette. Other additions include new methods like “list_users,” “list_groups,” “list_apps,” and “list_service_principals” to the main “ms_graph” client class. The package also includes a new “Authentication” vignette that guides users through different methods of authentication to Microsoft Graph.

AzureRMR

Similar to AzureGraph, AzureRMR introduced an updated “Authentication” vignette. This vignette details the process of authenticating to Resource Manager, replacing the old “Service Principal” vignette. Additionally, the Resource Manager API version was updated to “2021-04-01.” The “az_subscription$list_locations” function was also modified to handle the new response format in this API version.

AzureStor

The AzureStor package now includes support for generating a service SAS (Shared Access Signature). The new S3 generic function “get_service_sas” allows users to generate and retrieve a service SAS with methods for “az_storage” and “storage_endpoint” objects. Another method for “az_storage” objects was also included. The “storage_save_rds” and “storage_load_rds” functions were fixed to handle compression correctly, specifically in relation to files saved with the “saveRDS” function. Furthermore, a bug that caused the “list_blobs” function to fail when leases were present was resolved. In addition, the package now uses a raw connection instead of a raw vector when calling the “readr::read_delim” and “read_csv2” functions. This resolves an issue introduced in readr 1.4.0. The client API version was updated to “2020-04-08,” allowing users to specify the resource type when creating a service or user delegation SAS for blob storage. Finally, the “storage_endpoint” function now has an optional “service” argument, which allows users to specify the service in question (blob, file, ADLS2, queue, or table). This accommodates URLs that do not follow the usual pattern.

Microsoft365R

The latest version of the Microsoft365 package, Microsoft365R, introduces significant new features. In OneDrive and SharePoint, a new method called “list_shared_items” was added to the “ms_drive” class. This method enables users to access files and folders that have been shared with them. Another enhancement allows users to get drives for groups, sites, and teams by name. The first argument to the “get_drive” method for these classes is now “drive_name.” To get a drive by ID, the “drive_id” argument can be specified explicitly. Additionally, the “delete_item” method for drives and the “delete” method for drive items now have a “by_item” argument. This allows the deletion of non-empty folders on SharePoint sites with data protection policies in place.

In the Outlook module, a new “search” argument was added to the “ms_outlook_folder$list_emails” method. By default, this argument searches for emails in the “from,” “subject,” and “body” fields.

In the Teams module, the Microsoft365R package now includes the “list_members” and “get_member” methods for teams and channels. Additionally, support for mentions in Teams channel messages was added.

Other improvements include the addition of filter and n arguments to all “list_*” class methods, following the pattern established in AzureGraph. These arguments allow users to filter the result set and limit the number of results. The package also introduced experimental read-only support for plans, with contributions from Roman Zenka. The “az_group” class now includes the “get_plan” and “list_plans” methods, allowing users to retrieve and manage plans associated with Microsoft 365 groups.

Conclusion

The AzureR family of packages received significant updates in May and June 2021. These updates enhance various aspects of the packages, including authentication, paging API support, SAS generation, and new features in Microsoft365R. Users can take advantage of these updates to improve their experience and efficiency when working with AzureR packages.

Summary: “Exciting AzureR Updates Unveiled for May/June: Revolutionizing the Way You Work”

This is a summary of the updates to AzureR family of packages in May and June 2021. The updates include changes to AzureAuth, AzureGraph, AzureRMR, AzureStor, and Microsoft365R packages. In AzureAuth, the default caching behavior has been changed and a new function for creating caching directory manually has been added. AzureGraph has added enhanced support for the paging API and batch request feature. AzureRMR has a new Authentication vignette and updated the Resource Manager API version. AzureStor has added support for generating a service SAS and fixed bugs related to compression and file listing. Microsoft365R has added significant new features related to OneDrive/SharePoint, Outlook, and Teams.

Frequently Asked Questions:

Q1: What is Data Science?

A1: Data Science is a multidisciplinary field that involves extracting insights and knowledge from structured and unstructured data using scientific methods, algorithms, and tools. It combines domains such as statistics, mathematics, programming, and domain expertise to transform raw data into meaningful information.

Q2: What are the key skills required in a Data Scientist?

A2: A successful Data Scientist should possess a blend of technical and non-technical skills. Technical skills include proficiency in programming languages (Python, R, SQL), statistical analysis, machine learning algorithms, data visualization, and big data tools. Non-technical skills include critical thinking, problem-solving, communication, and domain knowledge in the specific industry.

Q3: How does Data Science impact businesses?

A3: Data Science has a profound impact on businesses across industries. By utilizing data analytics and predictive modeling techniques, businesses can make informed decisions, identify trends and patterns, optimize processes, anticipate customer behavior, and improve overall performance. It helps in maximizing efficiency, minimizing risks, enhancing customer experience, and gaining a competitive advantage in the market.

Q4: What is the difference between Data Science and Big Data?

A4: While Data Science and Big Data are related, they are distinct concepts. Data Science involves extracting insights from data, irrespective of the data size. It focuses on analyzing and interpreting data to solve specific problems and derive meaningful insights. On the other hand, Big Data deals with managing and processing enormous volumes of data that cannot be handled by traditional techniques. It involves storing, processing, and analyzing data with high velocity, variety, and veracity.

Q5: What are the ethical considerations in Data Science?

A5: Ethical considerations in Data Science revolve around privacy, transparency, bias, and accountability. Data Scientists must ensure the proper handling and protection of sensitive data. They should be transparent about the purpose and methods used in data analysis. Additionally, they should strive to eliminate bias in data collection, interpretation, and algorithmic decision-making. Data Scientists also need to be accountable for the consequences of their data-driven actions and be aware of the potential societal impact.