This article is part of our AZ-700 series, offering a step-by-step guide on configuring Azure Private DNS, based on the tutorial available on YouTube. I highly recommend watching the video to gain a solid understanding of the concepts covered in this article. Through this guide, you’ll gain hands-on experience in setting up and managing Azure Private DNS, enabling efficient DNS resolution, network segmentation, and seamless automation within Microsoft Azure.

In today’s cloud environment, managing network resources and ensuring secure connectivity across virtual networks (vNets) can be complex, particularly when DNS management comes into play. This article provides a comprehensive, hands-on guide to setting up and configuring Azure Private DNS for efficient DNS resolution, network segmentation, and seamless automation in Microsoft Azure. Follow along as we explore the essential elements, from linking vNets and subnets to DNS automation.

Why Azure Private DNS?

Azure Private DNS allows you to manage and resolve DNS names within a virtual network without exposing them to the public internet. It simplifies domain name resolution, enhances security, and enables automation for dynamic environments.

Key benefits of using Azure Private DNS:

• Dynamic DNS Management: Automatically updates DNS records for new or deleted resources, eliminating stale or “dangling” DNS entries.
• Domain Delegation: Allows centralized DNS management by delegating your corporate domain to Azure Private DNS.
• Enhanced Security: DNS records are automatically removed when resources are deleted, ensuring up-to-date and secure network configuration.

Quick Recap: Azure Networking Fundamentals

Before diving into Azure Private DNS, let’s revisit some foundational concepts from our previous discussions:

• vNet (Virtual Network): Similar to a traditional VLAN but without broadcast support, a vNet enables secure and scalable resource management.
• Subnet: Subdivision within a vNet, allowing more granular control over resource segmentation.

Azure allows you to set up a single vNet with multiple subnets, maximizing network organization and security without the broadcast overhead typical in traditional networks.

Step 1: Understanding Azure Private DNS

Azure Private DNS enables the automatic registration of DNS names for resources within your vNet. For example, when you create a virtual machine (VM) in a vNet linked to a private DNS zone, the VM’s name and IP address automatically register within the zone. This streamlines DNS management, especially for dynamic environments where resources are created and deleted frequently.

Key Features

• Automatic DNS Registration: Automatically updates the DNS zone with new or removed resources.
• Domain Delegation: You can delegate your corporate domain to the private DNS zone, managing DNS records centrally within Azure.
• Support for All DNS Record Types: Azure DNS supports a full range of DNS records, including A, AAAA, CNAME, and MX records.

Step 2: Setting Up the Private DNS Zone

1. Create a Private DNS Zone

• In the Azure Portal, navigate to Private DNS Zones and create a new zone.
• Define a name for the DNS zone, such as yourdomain.private.
• Deploy the DNS zone and navigate to the resource.

2. Link vNets for Automatic DNS Registration

• Within the Private DNS Zone resource, select Virtual Network Links to connect vNets to the DNS zone.
• For each vNet (e.g., Core Services, West Europe, Asia), specify the vNet link and enable Auto Registration.
• This enables seamless DNS name resolution across linked vNets and allows automatic DNS record updates when resources are created or deleted.

Step 3: Verifying DNS Resolution and Connectivity

1. Verify DNS Records in the Private DNS Zone: Go to DNS Management under the Private DNS zone and check that the A records for the VMs appear.
2. Connect to VMs via DNS:
   • Use Remote Desktop to access one VM, then attempt to connect to the other VM by its DNS name (rather than IP address). This confirms that the Private DNS setup allows for name-based connectivity.
   • If issues arise (e.g., timeouts), ensure that firewall settings permit connectivity between the VMs.

Step 4: DNS Zone Peering Across Regions

With Azure Private DNS, you can link vNets across different regions, allowing resources in different geographic locations to resolve names and connect seamlessly.

1. Link vNets Across Regions: Connect the vNets in regions like West Europe, East US, and Asia to the Private DNS zone.
2. Verify Regional Connectivity: From a VM in one region (e.g., Asia), test connectivity to a VM in another region (e.g., East US) using DNS names. Azure Private DNS allows DNS name resolution across regions, ensuring consistent and reliable network connectivity.

Summary

Setting up Azure Private DNS is a powerful way to automate and centralize DNS management within a virtual network environment. This guide provides a practical framework for deploying Private DNS zones, linking vNets, and verifying connectivity. By configuring Azure Private DNS, organizations can streamline DNS management, secure network configurations, and enhance connectivity across geographically dispersed resources.

Next Steps

In future tutorials, we’ll explore VNet peering for advanced network configurations, allowing secure communication between isolated virtual networks. Be sure to subscribe and stay tuned for more Azure networking tips and tricks!

Let’s enhance your Azure network management with practical, hands-on solutions.

​This article is part of our AZ-700 series, offering a step-by-step guide on configuring Azure Private DNS, based on the tutorial available on YouTube. I highly recommend watching the video to gain a solid understanding of the concepts covered in this article. Through this guide, you’ll gain hands-on experience in setting up and managing Azure Private DNS, enabling efficient DNS resolution, network segmentation, and seamless automation within Microsoft Azure.    In today’s cloud environment, managing network resources and ensuring secure connectivity across virtual networks (vNets) can be complex, particularly when DNS management comes into play. This article provides a comprehensive, hands-on guide to setting up and configuring Azure Private DNS for efficient DNS resolution, network segmentation, and seamless automation in Microsoft Azure. Follow along as we explore the essential elements, from linking vNets and subnets to DNS automation.Why Azure Private DNS?Azure Private DNS allows you to manage and resolve DNS names within a virtual network without exposing them to the public internet. It simplifies domain name resolution, enhances security, and enables automation for dynamic environments.Key benefits of using Azure Private DNS:Dynamic DNS Management: Automatically updates DNS records for new or deleted resources, eliminating stale or “dangling” DNS entries.Domain Delegation: Allows centralized DNS management by delegating your corporate domain to Azure Private DNS.Enhanced Security: DNS records are automatically removed when resources are deleted, ensuring up-to-date and secure network configuration.Quick Recap: Azure Networking FundamentalsBefore diving into Azure Private DNS, let’s revisit some foundational concepts from our previous discussions:vNet (Virtual Network): Similar to a traditional VLAN but without broadcast support, a vNet enables secure and scalable resource management.Subnet: Subdivision within a vNet, allowing more granular control over resource segmentation.Azure allows you to set up a single vNet with multiple subnets, maximizing network organization and security without the broadcast overhead typical in traditional networks.Step 1: Understanding Azure Private DNSAzure Private DNS enables the automatic registration of DNS names for resources within your vNet. For example, when you create a virtual machine (VM) in a vNet linked to a private DNS zone, the VM’s name and IP address automatically register within the zone. This streamlines DNS management, especially for dynamic environments where resources are created and deleted frequently.Key FeaturesAutomatic DNS Registration: Automatically updates the DNS zone with new or removed resources.Domain Delegation: You can delegate your corporate domain to the private DNS zone, managing DNS records centrally within Azure.Support for All DNS Record Types: Azure DNS supports a full range of DNS records, including A, AAAA, CNAME, and MX records.Step 2: Setting Up the Private DNS Zone1. Create a Private DNS ZoneIn the Azure Portal, navigate to Private DNS Zones and create a new zone.Define a name for the DNS zone, such as yourdomain.private.Deploy the DNS zone and navigate to the resource.2. Link vNets for Automatic DNS RegistrationWithin the Private DNS Zone resource, select Virtual Network Links to connect vNets to the DNS zone.For each vNet (e.g., Core Services, West Europe, Asia), specify the vNet link and enable Auto Registration.This enables seamless DNS name resolution across linked vNets and allows automatic DNS record updates when resources are created or deleted.Step 3: Verifying DNS Resolution and ConnectivityVerify DNS Records in the Private DNS Zone: Go to DNS Management under the Private DNS zone and check that the A records for the VMs appear.Connect to VMs via DNS:Use Remote Desktop to access one VM, then attempt to connect to the other VM by its DNS name (rather than IP address). This confirms that the Private DNS setup allows for name-based connectivity.If issues arise (e.g., timeouts), ensure that firewall settings permit connectivity between the VMs.Step 4: DNS Zone Peering Across RegionsWith Azure Private DNS, you can link vNets across different regions, allowing resources in different geographic locations to resolve names and connect seamlessly.Link vNets Across Regions: Connect the vNets in regions like West Europe, East US, and Asia to the Private DNS zone.Verify Regional Connectivity: From a VM in one region (e.g., Asia), test connectivity to a VM in another region (e.g., East US) using DNS names. Azure Private DNS allows DNS name resolution across regions, ensuring consistent and reliable network connectivity.SummarySetting up Azure Private DNS is a powerful way to automate and centralize DNS management within a virtual network environment. This guide provides a practical framework for deploying Private DNS zones, linking vNets, and verifying connectivity. By configuring Azure Private DNS, organizations can streamline DNS management, secure network configurations, and enhance connectivity across geographically dispersed resources.Next StepsIn future tutorials, we’ll explore VNet peering for advanced network configurations, allowing secure communication between isolated virtual networks. Be sure to subscribe and stay tuned for more Azure networking tips and tricks!Let’s enhance your Azure network management with practical, hands-on solutions.  Read More

​

Health and Life Sciences Fabric User Group present:

Mastering Fabric’s Metrics Layer

Live webinar

Tuesday, November 12

1:00-2:00 PM ET

Register here

​Microsoft Tech Community – Latest Blogs –Read More 

I’ve been an “Insider” for 10 years and am an MS Alumni.  At the moment, my system is very unstable, and I’m at 26120.2200 on DEV. The online “reset” by “Recovery” fails time after time, and the newest ISO I have for Win11 is for build 26000 from June of ’24.  Many, many quick crashes of various apps the debugger calls: 

Security check failure or stack buffer overrun - code c0000409 (first/second chance not available)
Subcode: 0x7 FAST_FAIL_FATAL_APP_EXIT 

 Teams will essentially crash silently over and over. Other apps do the same. I’m exhausted from restoring backups, and it’s no fun even if your backups/restores are successful.  If the system is unstable, it’s no good. I’ve run the built-in Memtest on my ASUS Maximus Z790 motherboard (with 128GB of RAM) OVERNIGHT. The Memtest also has a “let’s beat on your CPU test,” and I’ve run it OVERNIGHT.  BOTH with ZERO errors.  

When I try to download a newer ISO, my machine is blocked from downloading builds, getting an error “715-123130 and 0937e3ef-85ee-495e-9ead-1ec99007c5a4,” and I’m not using a VPN, nor any other hiding technology.

“Error

We are unable to complete your request at this time. Some users, entities and locations are banned from using this service. For this reason, leveraging anonymous or location hiding technologies when connecting to this service is not generally allowed. If you believe that you encountered this problem in error, please try again. If the problem persists, you may contact Microsoft Support – Contact Us page for assistance. Refer to message code 715-123130 and 2df76cc4-cbbe-4ec1-92be-c4e03ea143e4.”

I’m at my wit’s end.  So, how do I temporarily leave Windows Insider to get stable (like load 242H) and then come back in?

Thanks,

Steve

​I’ve been an “Insider” for 10 years and am an MS Alumni.  At the moment, my system is very unstable, and I’m at 26120.2200 on DEV. The online “reset” by “Recovery” fails time after time, and the newest ISO I have for Win11 is for build 26000 from June of ’24.  Many, many quick crashes of various apps the debugger calls: Security check failure or stack buffer overrun – code c0000409 (first/second chance not available)
Subcode: 0x7 FAST_FAIL_FATAL_APP_EXIT  Teams will essentially crash silently over and over. Other apps do the same. I’m exhausted from restoring backups, and it’s no fun even if your backups/restores are successful.  If the system is unstable, it’s no good. I’ve run the built-in Memtest on my ASUS Maximus Z790 motherboard (with 128GB of RAM) OVERNIGHT. The Memtest also has a “let’s beat on your CPU test,” and I’ve run it OVERNIGHT.  BOTH with ZERO errors.  When I try to download a newer ISO, my machine is blocked from downloading builds, getting an error “715-123130 and 0937e3ef-85ee-495e-9ead-1ec99007c5a4,” and I’m not using a VPN, nor any other hiding technology.”ErrorWe are unable to complete your request at this time. Some users, entities and locations are banned from using this service. For this reason, leveraging anonymous or location hiding technologies when connecting to this service is not generally allowed. If you believe that you encountered this problem in error, please try again. If the problem persists, you may contact Microsoft Support – Contact Us page for assistance. Refer to message code 715-123130 and 2df76cc4-cbbe-4ec1-92be-c4e03ea143e4.” I’m at my wit’s end.  So, how do I temporarily leave Windows Insider to get stable (like load 242H) and then come back in? Thanks,Steve  Read More

​

I am admin on my companies booking calendar, we have multiple technicians that are booked out to services by myself and the scheduler. There are technical team leads that can view their specific team’s availability and advise myself and the scheduler for work assignments.

Technicians are set up as guests on the calendar to be booked but without being able to view others calendars, team leads are set up as viewers to facilitate advising on scheduling. Recently there have been two technicians that were promoted to team leads, I updated their roles to viewer and they can’t see the calendar, they can find it by searching it for name but when they try to open it they are told they don’t have access to it.

Any advice on what may be causing this?

​I am admin on my companies booking calendar, we have multiple technicians that are booked out to services by myself and the scheduler. There are technical team leads that can view their specific team’s availability and advise myself and the scheduler for work assignments. Technicians are set up as guests on the calendar to be booked but without being able to view others calendars, team leads are set up as viewers to facilitate advising on scheduling. Recently there have been two technicians that were promoted to team leads, I updated their roles to viewer and they can’t see the calendar, they can find it by searching it for name but when they try to open it they are told they don’t have access to it.Any advice on what may be causing this?  Read More

​

Introduction

Effectively managing large document volumes is essential for modern applications, particularly to maintain fast and reliable querying. With Azure Logic Apps, you can now automate document indexing into Azure Cosmos DB, in addition to the existing capability of indexing in AI Search, offering the flexibility to use either service as a vector store.

Logic Apps offers a rich set of connectors that allow seamless integration with various document sources such as Azure Blob Storage, SharePoint, and OneDrive, enabling automated workflows for document ingestion from multiple locations. Whether you’re working with PDFs, Word documents, or structured data files like CSVs, Logic Apps supports parsing different document types efficiently.

For larger documents, Logic Apps can also implement chunking, breaking down files into manageable parts to optimize processing and indexing. This ensures even complex or large datasets are handled smoothly without overwhelming system resources.

In terms of integration with Azure Cosmos DB, the Logic Apps Cosmos DB connector supports multiple authentication methods, including Managed Identity, Shared Key Authentication, and Azure Active Directory OAuth, providing flexibility depending on your security requirements. Additionally, Logic Apps can meet various networking needs, such as integrating with private endpoints or using VNet integration to secure communication between services.

In this post, we’ll walk through a scenario where Logic Apps automates the ingestion and indexing of documents, such as PDFs, into Azure Cosmos DB. This approach not only reduces operational overhead but also ensures that your data remains highly accessible and queryable.

Why use Logic Apps for document indexing in Cosmos DB?

• Automated Workflows: By automating document indexing, you eliminate manual tasks and ensure that documents are indexed as soon as they are uploaded.
• Scalability: As your document volume grows, Azure Cosmos DB’s global distribution ensures your data remains scalable and highly available.
• Seamless Integration: Logic App enables you to easily integrate with other Azure services, such as Blob Storage and AI models, enhancing your document indexing with intelligence and automation.

Scenario Overview

In this scenario, we automate the ingestion of document content from Azure Blob Storage, parsing it, and indexing it into Azure Cosmos DB. When a blob (such as a PDF or text document) is uploaded, a Logic App workflow is triggered to process the document and store its data in a Cosmos DB container, making it easily retrievable and queryable.

Pre-requisites

To set up the scenario on your machine, please make sure to set up:

1. Azure CosmosDB resource to index data into
2. Azure Storage account to upload content to be indexed

Setting up Azure CosmosDB

Once you have created the resource:

1. Navigate to the Azure CosmosDB resource
2. From the “Settings” menu, select “Features”
3. Enable the feature for “Vector Search in Azure Cosmos DB for NoSQL”

The steps could also be found in detail in this blogpost from Azure CosmosDB. Now that you have the CosmosDB resource setup as an index store, let’s create a new database and a container for the vector store database.

To create a new container:

1.  Navigate to “Data Explorer”
2. Create a “New Container” with the following field set for:
   1. Database id: This is your databaseID, in our case it is ‘docs’
   2. Container id: Container in which your documents will be stored, we have it defined as ‘category’
   3. Partition key: for data distribution, we have defined it as ‘/category”, given there could be other categories of documents you may want to query that have been indexed.
3. Container Vector Policy: this is where we set the vector properties for ‘Vector Embedding 1
   1. Path: where to search and represent the vector embeddings from. In our case it will be ‘/vector’.
   2. Data type: float32
   3. Distance function: this will be used to determine distance between the closest neighbors. In our case set it to ‘cosine’
   4. Dimensions: 1056
   5. Index type: diskANN, as it is low-cost, scalable and improved latency option for finding Approximate Nearest Neighbors (ANN)

You can find more information on the container set up from this GitHub tutorial.

Document Structure for Indexing in Azure Cosmos DB

In this Logic Apps workflow, we’re indexing document embeddings into Azure Cosmos DB. Below is a breakdown of the key fields we’re mapping and indexing:

1. content: This field holds the main body of the document or the actual text content that has been processed. For example, this could be the textual data extracted from a document like a contract, invoice, or any other file type.
2. documentName: The name or title of the document being indexed. This field helps in identifying the document based on its file name, making it easier to search and retrieve the document by its original name.
3. vector: This represents the embeddings vector of the document, which is a numerical This irepresentation of the content. These vectors are used to perform similarity searches on documents, allowing for AI-driven insights or matching based on content similarity.
4. docId: A unique identifier generated for each document. This ensures that each document has a distinct ID, which is crucial for querying and updating specific items in the Cosmos DB container.
5. category: This is where the document type or category is assigned. In our case, we’re using “documents” as the value for this field. This helps in classifying and grouping documents, which can be useful when querying for specific types of documents within the database.
6. id: Another unique identifier, often auto-generated or derived by concatenating values. This ID could be used to ensure that there is no duplication and that each document is properly referenced

It will look like this when we compose the payload to pass in Azure CosmosDB from logic app workflow:

Key Steps in the Workflow

I have added a GitHub sample for the workflow project. Here’s a visual representation of the workflow:

1. Blob Upload Detection: The Logic App starts by detecting when a new blob (document) is added or updated in Azure Blob Storage.
2. Read Blob Content: The workflow reads the content of the uploaded blob and prepares it for further processing.
3. Document Parsing: Logic Apps parses the document, extracting the relevant content, such as text or metadata. This can include PDF extraction or text chunking for larger documents.
4. Chunk Text (if needed): For larger documents, the content is split into manageable chunks to ensure smooth processing and indexing.
5. Generate Embeddings Using AI: Using Azure AI, the Logic App generates embeddings from the document content. These embeddings allow for enhanced data processing, categorization, and structure mapping within Cosmos DB.
6. Map to Schema: The extracted data and embeddings are mapped to a predefined schema to ensure consistency in how documents are indexed within Cosmos DB. Here are the properties we are indexing:
7. Bulk Update in Cosmos DB: Finally, the processed document is stored and indexed in Cosmos DB. The “Create or update many items in bulk” action accepts the database and container ID alongside the data to be indexed in which multiple items are processed into the database from previous action.

Conclusion

By leveraging Azure Logic Apps to automate document indexing into Azure Cosmos DB, you can streamline data workflows, reduce manual intervention, and ensure your data is organized for optimal performance. This powerful integration simplifies the process, making it easier for teams to manage large volumes of documents and scale as needed.

What’s next

Currently, Logic Apps support efficient document indexing, but Vector search for AI-driven retrieval is not yet available in Azure CosmosDB. This much-anticipated feature that will enhance Cosmos DB as a powerful vector store. Stay tuned for this update!

​Microsoft Tech Community – Latest Blogs –Read More 

I want to share Excel files and Word documents with people outside my organization (MS Tenant). I am thinking of doing this by connecting my SharePoint folder with a Dropbox folder. Is there an app for this? Or is there another way to share files with outside people?

​I want to share Excel files and Word documents with people outside my organization (MS Tenant). I am thinking of doing this by connecting my SharePoint folder with a Dropbox folder. Is there an app for this? Or is there another way to share files with outside people?  Read More

​

On my email account at outlook.com, I have a number of pinned emails at the top. Suddenly, they are no longer there! I’d like to get them back.

Jeff

​On my email account at outlook.com, I have a number of pinned emails at the top. Suddenly, they are no longer there! I’d like to get them back. Jeff  Read More

​

I have a second work email, with a client. I have an outlook account, Office 365 account and the client’s office 365 acccount.  I set up a auto-forward rule in the client’s account to my hotmail  and my 365 email  .  The forward fails with this message: 

Delivery has failed to these recipients or groups:

email address removed for privacy reasons (email address removed for privacy reasons)
Your message wasn’t delivered because the recipient’s email provider rejected it.

Diagnostic information for administrators:

Generating server: SJ0PR16MB5057.namprd16.prod.outlook.com

email address removed for privacy reasons
Remote server returned ‘550 5.7.520 Access denied, Your organization does not allow external forwarding. Please contact your administrator for further assistance. AS(7555)’

I’ve added all emails as contacts in the three outlooks.  Any other ideas? I hate having to have three emails open on my desktop and bouncing between them.

TIA John

​I have a second work email, with a client. I have an outlook account, Office 365 account and the client’s office 365 acccount.  I set up a auto-forward rule in the client’s account to my hotmail  and my 365 email  .  The forward fails with this message:  Delivery has failed to these recipients or groups: email address removed for privacy reasons (email address removed for privacy reasons)Your message wasn’t delivered because the recipient’s email provider rejected it.Diagnostic information for administrators:Generating server: SJ0PR16MB5057.namprd16.prod.outlook.comemail address removed for privacy reasonsRemote server returned ‘550 5.7.520 Access denied, Your organization does not allow external forwarding. Please contact your administrator for further assistance. AS(7555)’ I’ve added all emails as contacts in the three outlooks.  Any other ideas? I hate having to have three emails open on my desktop and bouncing between them. TIA John  Read More

​

Hello,

I would like to know how to restore the option of selecting the date in the searching options menu in the explorer of windows. It seems that it has disappeared on its own for about 1 month and only offers me these choices as shown in the attached photo 1. I have searched but no option has been able to include the famous option. Is there a connection with the indexing which is suspended as shown in image 2.Even the windows toolbar for indexing errors didn’t help me to restore the function,

Please i just want to recover this useful function by just clicking on the calendar and choose the file to display by specific date.The other options like putting in search bar dates does not respond to my needs.

And i am totally suprised why or how the option has disappeared from the menu since 1 month.It displays only:today, yesterday, last month, etc but the calendar with choosing is no more availbale?!

Thank you for helping me to set it up again please!

​Hello, I would like to know how to restore the option of selecting the date in the searching options menu in the explorer of windows. It seems that it has disappeared on its own for about 1 month and only offers me these choices as shown in the attached photo 1. I have searched but no option has been able to include the famous option. Is there a connection with the indexing which is suspended as shown in image 2.Even the windows toolbar for indexing errors didn’t help me to restore the function, Please i just want to recover this useful function by just clicking on the calendar and choose the file to display by specific date.The other options like putting in search bar dates does not respond to my needs.And i am totally suprised why or how the option has disappeared from the menu since 1 month.It displays only:today, yesterday, last month, etc but the calendar with choosing is no more availbale?! Thank you for helping me to set it up again please!  Read More

​

Back in 2012, when our company began using Sharepoint, we set up different subsites for each function. eg.: HR, Accounting, Sales, Operations, Customers.  Within these subsites we set up document libraries to organize the data.  In these libraries we store customer communications, job photos, and diagrams related to each jobsite. Each library is labeled with the customer name and/or address. This was working great until last week when we reached our limit of 500 customer libraries. 

I have created an additional Customer subsite for a specific division to move some of the libraries in an attempt to free up room in the original site.  I have moved about a dozen libraries to the new site and deleted some others.  The original site is still not allowing new document libraries to be added.  How can the library limit be reset to the current value to allow additional libraries?  Or what is the best way to move select document libraries to a new site in bulk? 

Your assistance is greatly appreciated.

AM

​Back in 2012, when our company began using Sharepoint, we set up different subsites for each function. eg.: HR, Accounting, Sales, Operations, Customers.  Within these subsites we set up document libraries to organize the data.  In these libraries we store customer communications, job photos, and diagrams related to each jobsite. Each library is labeled with the customer name and/or address. This was working great until last week when we reached our limit of 500 customer libraries.  I have created an additional Customer subsite for a specific division to move some of the libraries in an attempt to free up room in the original site.  I have moved about a dozen libraries to the new site and deleted some others.  The original site is still not allowing new document libraries to be added.  How can the library limit be reset to the current value to allow additional libraries?  Or what is the best way to move select document libraries to a new site in bulk?  Your assistance is greatly appreciated. AM  Read More

​